DevelopersOsai website ↗
API v1
Settlement reports / API reference

Get settlement by ID

Request and response reference for GET /v1/settlements/{settlement_id}.

GET/v1/settlements/{settlement_id}
Authentication: API key
Use the base URL and access configuration provided to your institution. Examples are request templates, not transaction results. Field tables focus on client fields; preserve additional metadata returned by the configured service.

Request

Keep API keys in your backend. Required entitlements and institution scope still apply.

Request templatecURL
curl -X GET "$OSAI_API_BASE_URL/v1/settlements/$SETTLEMENT_ID" \
  -H "Authorization: ApiKey $OSAI_PUBLIC_ID:$OSAI_API_SECRET"

Parameters

NameLocationRequirementDescription
Authorizationheader · stringRequiredUse the value defined for this resource.
X-Request-Idheader · stringOptionalUse the value defined for this resource.
settlement_idpath · stringRequiredUse the value defined for this resource.

Request body

This operation does not define a JSON request body.

Responses

Inspect HTTP status before parsing a body. These tables describe client response fields rather than invented successful transaction payloads.

200 · Settlement found
FieldTypeDescription & constraints
settlement_idRequired in parent objectstringDefined by the resource contract.
trade_idRequired in parent objectstringDefined by the resource contract.
quote_idRequired in parent objectstringDefined by the resource contract.
institution_idRequired in parent objectstringDefined by the resource contract.
statusRequired in parent objectstringDefined by the resource contract.
beneficiaryOptionalstringDefined by the resource contract.
amount_minorRequired in parent objectintegerDefined by the resource contract.
currencyRequired in parent objectstringDefined by the resource contract.
purposeOptionalstringDefined by the resource contract.
request_idOptionalstringDefined by the resource contract.

Retries & recovery

Keep the original request identifiers and any required idempotency key. A timeout does not establish failure. Read the original resource or command before another financial write; use expected versions for concurrent changes.

16 suggested pages

Get startedIntroductionIntegrate institutional FX and stablecoin trading with quotes, orders, market data, account records and settlement reporting.Get startedQuickstartMake an authenticated read, request a quote and follow an instruction without losing its original references.Get startedAuthenticationUse the correct authentication scheme for API credentials, Console sessions and market-data feeds.Get startedErrorsDistinguish invalid inputs, denied access, conflicts, rate limits and uncertain outcomes.Get startedRate limitsUse response headers, bounded concurrency and backoff rather than repeated bursts.Get startedAmounts & precisionKeep minor-unit money, fixed-point FX rates and instrument-scaled quantities exact.Get startedPagination & recoveryUse each resource’s pagination model and preserve stable recovery checkpoints.Financial workflowsQuotes & acceptanceRequest explicit FX economics, review conditions and retain accepted terms.Financial workflowsTrade lifecycleTrack funding, execution and settlement as distinct business transitions.Financial workflowsBalances & transactionsRead institutional financial positions and reconcile movements by currency.Financial workflowsBeneficiariesRegister beneficiaries and coordinate their institutional approval lifecycle.Financial workflowsCredential managementCreate, inspect, rotate and revoke application credentials without exposing secrets.Events & reliabilityIdempotencyPrevent duplicate financial effects across retries and uncertain outcomes.Events & reliabilityWebhooks & verificationVerify deliveries, persist original events and make downstream processing idempotent.Events & reliabilityEvent payloadsUnderstand the customer event envelope and business transitions behind subscriptions.Events & reliabilityDelivery retries & replayRepair webhook delivery without creating a second business event.