Get localization locales

Discover supported display locales, the default locale, batch limit and original-only rules policy. Uses your market-data access; no additional configuration for your organization or translation service is required.

Multilingual market displays guide · All endpoints · SDK: getLocalizationLocales

Authentication

Request fields

Required means the field must be present. Nullable means an explicit JSON null is allowed; it does not mean optional.

JSON body

No request body.

Request example

Illustrative identifiers only: replace them with resources from your integration. Keep credentials on your backend. HTTP placeholders must be signed; the SDK signs automatically. Financial intent keys must be persisted and unique per new action.

GET /v1/localization/locales
Host: partner-api.crisp.trade
X-Crisp-Partner-Key: <server-key-id>
X-Crisp-Timestamp: <fresh-ISO-8601-UTC-timestamp>
X-Crisp-Nonce: <fresh-unique-nonce>
X-Crisp-Signature: <computed-base64-HMAC>

Response fields

HTTP responses use the envelope below. SDK calls expose its payload as result.data, with HTTP status and request metadata on the SDK wrapper.

Response example

Schema illustration, not live account data. Null means unavailable or not applicable, never an invented zero. Empty arrays do not imply the endpoint always returns no results.

{
  "data": {
    "locales": [],
    "defaultLocale": "en",
    "maxBatchSize": 0,
    "rulesPolicy": "original_only"
  },
  "requestId": "example-request-id"
}

Errors and recovery

Inspect the error code and outcomeUnknown, not just the HTTP status. Preserve the original intent after financial uncertainty. Read-only retries should honor Retry-After. Recovery workflow →

Raw contract

OpenAPI download · Advanced schema and legacy anchor