Skip to main content
GET
Get the latest rates from one base currency
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 when your application needs a table of available rates from one base currency—for example, a price-display setting or a back-office conversion view. The response excludes the base code from data.rates.

API endpoint

GET

Request

curl

Response

The rate map below is shortened for readability. data.rates contains the full set of rates available for the requested base currency.

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. base must be an active three-letter currency code. AvraAPI accepts lower-case input and normalises it before validation, but use uppercase codes in your application for clarity. An unknown or inactive value returns 400 with error.code: invalid_currency_code.

Read last_updated correctly

data.last_updated is the current source-update value held by AvraAPI. It is useful for freshness checks, but its exact string format is not a versioned contract. Do not use this endpoint as a financial quote or settlement source without your own validation. Use Get one currency-pair rate when you only need one target rate.

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

Path Parameters

base
string
required

An active three-letter currency code. Input is normalised to uppercase before it is checked against the active Currency code list.

Pattern: ^[A-Za-z]{3}$
Example:

"USD"

Response

Current rates from the requested base currency.

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