Avoiding API timeouts

Timeouts happen if a service takes more than 30 seconds to respond to a call. If a timeout occurs, you’ll see the 500 error status code with details about the timeout in the response.

Timeouts are typically caused by one of two things:

  • The call involves too much data
  • There is a network/service issue

If one of your calls times out, we recommend first re-trying the call after a few seconds of idle time, since it may have been caused by a network issue that has resolved itself. You should re-try at least three times, to allow time for any network issues to resolve.

If you think the data you’re working with might be too large, we recommend checking whether a bulk, list, or batch service is available to achieve the response you’re looking for. These types of operations are designed for use with large amounts of data.

Related links

Introduction to the Replicon API
Using the API
Getting started with Replicon's API
Rate limiting
API authentication
A Gateway Timeout error occurs when accessing Replicon