Request Timeout

Klarna API request timeout behavior for Direct Partners: default idle timeouts, the structured timeout error response, and recommendations for retrying timed-out requests safely.

1 min read

Request Timeout

To improve integration resilience, it is a best practice to configure explicit timeouts for all API requests made to Klarna APIs.

Klarna API timeout behavior

All Klarna APIs enforce an idle timeout, a limit on how long a connection can remain open without returning data.

Default idle timeout: 59 seconds
Some API operations define shorter timeouts, which are specified in their individual API operation documentation.
Note: An API request may take longer than 59 seconds if the connection remains active and data continues to be transferred. This situation is rare and should not be relied upon for typical operation.

Error response for timeout

If the timeout is reached before a response is returned, Klarna's API responds with HTTP status code 500 and a structured error object indicating a timeout condition:

JSON

1 2 3 4 5 6

{
  "error_id": "8e3a4d0c-3b0a-4b1e-9a3e-2a2a1f2e4e77",
  "error_type": "TECHNICAL_ERROR",
  "error_code": "TIMEOUT",
  "error_message": "Request processing timeout."
}

error_code is TIMEOUT when an action's shorter timeout is reached, and INTERNAL_ERROR when the default timeout is reached.

Retrying Timed-Out Requests

Timed-out requests can be retried, following the recommendations outlined in the Idempotency documentation.

Jump to section...