Rhonda Glennon
9 years ago
2 changed files with 20 additions and 0 deletions
@ -0,0 +1,19 @@ |
|||||||
|
# HTTP status codes |
||||||
|
|
||||||
|
## Geocoding |
||||||
|
|
||||||
|
The following status codes are returned from the geocoding service: |
||||||
|
|
||||||
|
- `200 OK`: The request has succeeded. |
||||||
|
- `400 Bad Request`: An input parameter was invalid. An error message is included in the response body with more details. |
||||||
|
- `404 Not Found`: The URL is invalid or the path is no longer valid. |
||||||
|
- `408 Request Timeout`: The Elasticsearch cluster took too long to respond. |
||||||
|
- `500 Internal Server Error`: Generic fatal error. |
||||||
|
- `502 Bad Gateway`: Connection was lost to the Elasticsearch cluster. |
||||||
|
|
||||||
|
In all cases above, the response body will be valid geoJSON. |
||||||
|
|
||||||
|
## Rate limiter |
||||||
|
The rate limiter returns the status codes `403 Forbidden` and `429 Too Many Requests`. |
||||||
|
|
||||||
|
See [API keys and rate limits](/api-keys-rate-limits.md) for more information. |
Loading…
Reference in new issue