DevelopersOsai website ↗
API v1
Console operations / API reference

List Internal Statements

Request and response reference for GET /v1/console/operations/statements.

GET/v1/console/operations/statements
Authentication: UnauthenticatedPermission: reports.read
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

This entry point does not require an existing session. Applicable onboarding, origin and verification policies still apply.

Request templatecURL
curl -X GET "$OSAI_CONSOLE_BASE_URL/v1/console/operations/statements"

Parameters

No endpoint-specific path or query parameters are defined. Authentication and access policy still apply.

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 · Current-human scoped internal Ledger statement response
FieldTypeDescription & constraints
statementsRequired in parent objectarrayDefined by the resource contract.
statements[].statement_idRequired in parent objectstringDefined by the resource contract.
statements[].fromRequired in parent objectstringdate-timeDefined by the resource contract.
statements[].toRequired in parent objectstringdate-timeDefined by the resource contract.
statements[].captured_atRequired in parent objectstringdate-timeDefined by the resource contract.
statements[].content_hashRequired in parent objectstringDefined by the resource contract.
limitRequired in parent objectintegerDefined by the resource contract.Values: 50
401 · Named session required

No client body fields are defined for this response.

403 · Current permission/MFA/CSRF denied

No client body fields are defined for this response.

404 · Scoped statement absent

No client body fields are defined for this response.

409 · Invalid period, future end or command conflict

No client body fields are defined for this response.

413 · Full result exceeds bound; narrow window; no truncated snapshot stored

No client body fields are defined for this response.

503 · Source/authority unavailable or outcome unknown; no fallback

No client body fields are defined for this response.

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.