Understand the most common errors you may experience using the Forefront API.
Forefront uses conventional HTTP response codes to indicate the success or failure of an API request. In general: Codes in the 2xx range indicate success. Codes in the 4xx range indicate an error that failed given the information provided (e.g., a required parameter was omitted, authentication issue, etc.). Codes in the 5xx range indicate an error with Forefront's servers (these are rare).
HTTP Status Code
200 - OK
Everything worked as expected.
400 - Bad request
The request was unacceptable, often due to a missing parameter.
401 - Unauthorized
No valid API key provided.
403 - Out of credits
Ran out of credits. Can be fixed by adding a payment method.
404 - Not found
The requested resource doesn't exist. Make sure you're using the correct API URL (pay-per-token vs. resource). If using a resource, make sure it is turned on and live (green dot).
422 - Incorrect parameter
Make sure the body is being sent as JSON. i.e. Add application/json header. Make sure the data types for the parameters are correct.
500, 502, 503, 504 - Server errors
Something went wrong on Forefront's end (this is rare).
Last modified 7mo ago