getneo
  1. Technical topics
getneo
  • Introduction
  • API examples
  • Technical topics
    • API structure
    • HTTP headers
    • Decoupled responses
    • Validation failures (418)
  • Endpoints
    • Auth
      • Get service bearer token (password)
        GET
      • Change tenant
        GET
      • End session
        GET
    • Counterparties
      • Get all counterparties
        GET
      • Get counterparty by ID
        GET
      • Get draft counterparty by ID
        GET
      • Submit counterparty draft
        POST
      • Update counterparty draft
        POST
      • Delete a counterparty draft
        DELETE
      • Add account to counterparty
        POST
      • Update counterparty account
        PATCH
      • Export counterparty data
        POST
    • Payments
      • Get all payments
        GET
      • Get a payment by ID
        GET
      • Make a payment (deposit, withdrawal or internal)
        POST
  1. Technical topics

Decoupled responses

For requests are taking longer to return than expected, the default behaviour of the API service is to return a "decoupled response".
This takes the form of a 202 Accepted response, containing a Location header for where to check for the result.
An X-Delay response header shows the current number of milliseconds that the next check must wait for at the minimum. This number can change between checks.
In order to force the service to block the initial response until a result is available, the X-PreventDecouple: true request header can be sent.
Example: Default decoupled response
250ms delay
Example: Blocking response
Wait
Modified at 2025-07-24 14:04:37
Previous
HTTP headers
Next
Validation failures (418)
Built with