Response Time & Timeout

Response Time & Timeout

API response times

API response times can vary based on several factors, including:

• The type of API and HTTP method used

• The amount of information returned

• Request complexity and backend processing

• Network conditions

API timeout behavior

All APIs have a configured timeout. In case of a timeout, the behavior differs for GET versus POST/PATCH APIs.

GET APIs

• If a timeout occurs, the client must resend the request.

Example timeout response (GET):

API operation has Time out. Request has been received but it has timeout before we receive the response. Please try again later.

POST / PATCH APIs

• If a timeout occurs, the system will continue to process the request.

• The client must verify whether it completed successfully using the appropriate GET APIs.

Example timeout response (POST/PATCH):

API operation has Time out. Request has been received and is has timeout before we receive the response. Please verify the request has been completed successfully or not. using the appropriate APIs.

Timeout values

• Default timeout: 30 seconds

Exceptions (higher timeout)

The following APIs are configured with 180 seconds timeout:

• Modify Destination Group

• Modify Roaming Profile

• Get Endpoint Profile

• Create Endpoint

• Link SIM

• De-Link SIM

• Endpoint Activation

• Endpoint LifeCycle Change

Notes

• For GET APIs: a timeout implies you should retry.

• For POST/PATCH APIs: a timeout does not necessarily indicate failure—always validate by querying the final state.