This page describes how Metronome uses HTTP status codes to indicate whether an API request succeeded or failed. It helps you interpret and handle different types of errors. Metronome uses standard HTTP status codes:
  • 2xx indicates success
  • 4xx indicates a client error (e.g., a required parameter was omitted)
  • 5xx indicates a Metronome server error
Every 4XX error uses this application/json format: 
{
  "message": "Descriptive error text"
}
The table lists the most common HTTP status codes returned by the Metronome API, along with a possible solution.
CodeMeaningDescriptionPossible solution
200OKEverything worked as expectedN/A—the request was successful
400Bad RequestThe request was unacceptable, often due to malformed syntax, or a missing or malformed parameterEnsure request syntax is correct
401Invalid access tokenRequestor is unauthorized or does not have permission for this API callEnsure API token is valid
403ForbiddenRequestor does not have access to this resourceEnsure API token is valid
404Resource not foundThe requested resource does not existEnsure ID of requested resource is valid
409ConflictThe request could not be processed due to a conflict with the current state of an existing resourceEnsure that the object doesn’t already exist, and if using an Idempotency-Key header, check that it’s unique
429Too Many RequestsToo many requests hit the API too quicklyWait and try again later
5XXServer ErrorsSomething went wrong while servicing your requestRetry your request. If using Idempotency-Key header, verify that resource was not partially created and retry using a different key