This page is generated from the contract (data/gateway-v1.json): each operation shows its verb, path, parameters, body, responses, whether it carries an Idempotency-Key, and the equivalent method in all five SDKs. For the end-to-end flow with complete examples, see the implementation guide.

Operations in tag transactions #

Contract description: Asynchronous transaction status lookup.

MethodPathOperationScopeIdem.
GET/v1/gateway/transactions/{tx_id}/Transaction status——

Transaction status #

GET/v1/gateway/transactions/{tx_id}/

  • operationId getTransaction
  • Authentication X-API-Key · any valid key
  • Idempotency-Key not applicable

Parameters

NameInTypeDescription
tx_id requiredpathstringGateway transaction id. E.g.: a1b2c3d4-0000-4a1b-9c2d-000000000001

Responses

CodeDescriptionBody
200Transaction record.TransactionStatus application/json
Possible errors (400, 401, 403, 404, 409, 422, 429, 500) — application/problem+json
400Malformed request.about:blank
401Missing or invalid API key.about:blank
403The key is valid but lacks the required scope, or the source IP is not allow-listed.about:blank
404The requested resource does not exist.about:blank
409Idempotency conflict — same key, original still processing.https://errors.compense.co/gateway/idempotency-conflict
422Request body failed validation.https://errors.compense.co/gateway/validation
429Per-key rate limit or monthly quota exceeded; see Retry-After.https://errors.compense.co/gateway/rate-limited
500Unexpected gateway error; quote the trace_id to support.about:blank

See problem+json errors for the equivalent exception in each SDK.

Example

SDK method and HTTP request
client.transactions.get()

Each SDK's methods come from its contract parity suite. The cURL runs against the sandbox; <field> values are placeholders.