Jump to main content

Guide

Everything you need to make the first request.

The base URL is shown on the home page and at the start of each example. The dataset name with a .json extension is added to it.

The data is served as-is; on the client side it only needs to be parsed.

Do I need a token

No. The service neither requires nor checks a token, an authorization header or a cookie.

A request comes down to opening an address; everything else is the client's business.

Stable addresses

A dataset address is a contract. While it lives, the response shape is predictable.

We announce the retirement of a version in advance on the documentation page.

Errors

The service answers with standard HTTP codes. A successful response comes with code 200 and a JSON body.

If a dataset or record is missing, you get 404. On too many requests, 429; try again later.

How the response is shaped

Each object in the array describes one record: a country, currency, zone or unit. The set of fields is the same for every record in a dataset.

We avoid empty and optional fields so parsing stays simple.

HTTP codes

CodeMeaning
200Request succeeded; the body is JSON.
404No such dataset or record.
429Too many requests, try again shortly.