Error handling

Errors are indicated by standard HTTP status codes. There are some error types that require special handling.

It is essential to ensure that your application properly handles errors. To achieve this, please review the list of expected status code results provided in each endpoint's documentation within the API Reference. Errors are indicated by standard HTTP status codes.

• HTTP 429: too many requests.

  To prevent receiving errors from sending too many API requests in a short period, configure your application to resend requests after a delay. We recommend implementing retries with exponential backoff.

• HTTP 500: internal server error

  If you encounter temporary errors in CropLink Services, configure your application to resend requests after a delay. It's recommended to implement retries with exponential backoff.

• HTTP 403: invalid ability provided.

  The authentication token in the header is invalid or does not have the necessary permissions.

Additional information may be provided by a JSON response that contains more details about the error. In this case, this additional information will be contained in the message key.