Skip to main content
GET
List supported currency codes
Live Testing Guide: Before using Try it, create a Development project, then enter its Client ID and Client Secret. Configure the relevant provider for that project before sending the request.
Use this route before rendering a currency selector or accepting a currency code from a user. It returns the active set at request time, so do not hard-code the count or assume every ISO 4217 code is enabled. The response includes standard codes such as USD and LKR, plus the CBSL target codes LKR-SELL, LKR-BUY, and LKR-CBSL when active. Those three are valid only as a target in the pair routes; they are not ordinary currencies to use as a base.

API endpoint

GET

Request

curl

Response

The list below is shortened for readability. data.codes contains every active code returned by the API.

Error codes

All failures use the standard AvraAPI error envelope. Keep the request_id when contacting support; see the REST API guide for the shared response format.

Use the response safely

Cache the list only for the lifetime that makes sense for your UI and refresh it from the endpoint before relying on a newly added or removed code. Keep request_id with support records when a code unexpectedly becomes unavailable. For CBSL target meanings and the direct-data fallback rule, read CBSL Rates.

Playground resources

The generated reference below lists this endpoint’s API standard details: request fields, authorizations, and response schema. The complete integration guide, request and response examples, and endpoint-specific error handling are above.

Authorizations

X-API-KEY
string
header
required

Your Development project's Client ID. Enter your own value in the Documentation Playground.

X-API-SECRET
string
header
required

Your Development project's Client Secret. Mintlify does not proxy these requests; the browser sends them directly to AvraAPI. Never enter a Production secret in the Documentation Playground.

Headers

X-ENV
enum<string>
default:development

Selects the Development credential environment. The Documentation Playground exposes Development values only; normal backend integrations may use their documented Production credentials outside this tool.

Available options:
dev,
development
Accept
string

Requests a JSON response where the selected operation supports JSON.

Example:

"application/json"

X-Privacy-Mode
boolean
default:false

Optional privacy override. Turn this on to request that AvraAPI suppress request-payload storage in observability logs for this request.

Example:

true

Response

Active currency codes.

success
enum<boolean>
required
Available options:
true
request_id
string<uuid>
required

Include this value when contacting AvraAPI support.

data
object
required

Operation-specific result data.

Last modified on October 1, 2026