400 | A parameter or body field is invalid or is not one the route takes, with each problem listed in an issues array. A refused paging cursor, or a request that a record’s current state does not allow, also returns 400; the message says why. |
401 | The key is missing, unknown, revoked, or does not hold a claim the route needs. |
403 | A write was sent as application/x-www-form-urlencoded, multipart/form-data or text/plain. Its body is not the error object above. |
404 | The route does not exist, or the record does not exist for your business. |
405 | The route does not take the request’s method. The Allow header lists the methods it does take. |
415 | A body was sent without Content-Type: application/json. A form or plain-text write gets the 403 instead. |
500 | Something failed on our side. Retry. |
