Errors - Specter API

Specter returns all error responses as JSON so you can programmatically detect, log, and fix problems seamlessly.

{
  "errorCode": "API_KEY_MISSING",
  "message": "No API Key was presented on the header X-API-KEY",
}

errorCode – machine‑readable identifier message – human‑friendly explanation with a potential fix‑it hint

Code	Comment
`400`	There was a problem with the request, it may be missing a field or a have a malformed field. This will not credit limit you, but will rate limit you.
`401`	The request is unauthenticated, the API key was supplied, but it is not a valid key. In this case please check your key and try again, if it continues then contact support.
`402`	Returned with an errorCode of `OUT_OF_CREDITS` when your team has no credits left for the current billing period. Check the `X-CreditLimit-Reset` header for when credits renew, or contact support to increase your allowance.
`403`	Your API key is correct, but you do not have access to this endpoint. This may happen if your subscription plan does not allow you access to the endpoints. For instance if you are not signed up to the company API but try to access it.
`404`	If the requested resource does not exist then this will be returned.
`422`	If there was a problem with validation then this will be returned, the `message` field of the response will have information about how to fix this, if this does not help then please contact Specter support.
`429`	Returned if you have been rate limited, i.e. you sent too many requests per second. Check the `X-RateLimit-Reset` header for when the limit resets.
`50x`	There was an internal error, in this case we will not credit limit you, but we may have rate limited you