Errors and limits
The status codes the GeotechOS API answers with, the shape of an error, the request limit, and the request id to give support.
This page lists what the API answers when a request does not succeed, and how many requests you can send.
Status codes
| Status | Meaning |
|---|---|
200 |
Done. The record was updated, or read |
201 |
Done. The record was made |
401 |
No key, an unknown key, or a key that was rotated or removed |
403 |
The integration is disabled, or the account it acts as cannot do this |
404 |
Nothing matches the name you sent |
409 |
A conflict that a person must decide, for example a client already linked to another of your ids |
422 |
The request has a problem. The errors field says which field and why |
429 |
Too many requests. Wait for the seconds in Retry-After |
500 to 504 |
A problem in GeotechOS. Try again later |
The shape of an error
An error has a message. A 422 also has errors, keyed by the field you sent:
{
"message": "No active account here uses: [email protected].",
"errors": {
"assignee_emails": ["No active account here uses: [email protected]."]
}
}
Request limit
Each key can send 300 requests in a minute. Every answer has these headers:
| Header | What it tells you |
|---|---|
X-RateLimit-Limit |
The requests allowed in a minute |
X-RateLimit-Remaining |
The requests left in this minute |
Retry-After |
On a 429, the seconds to wait |
A backfill of thousands of records goes faster than this. Wait when you get a 429, then continue.
Request id
Every answer, errors too, has an X-Request-Id header. Keep it with any error you log. Give it to GeotechOS support, and they can find that request.