POST
Add a currency the store can price and sell in

Authorizations

Authorization
string
header
required

A secret API key. Publishable keys cannot reach this API. A key may carry an expiry, and an expired key is refused exactly like an unknown one, with a 401 that names no reason; check the key's expires_at in the dashboard rather than inferring it from a response. When a merchant rolls a key's secret they choose a grace window of up to 3 days, and for its duration BOTH the new secret and the one it replaced authenticate, so an integration moves over on its own deploy schedule instead of at the instant the button is pressed. Move before the window closes: after it, the old secret is refused. Nothing else about this contract moves with a roll. The key keeps its id and its scopes, so the only thing an integration updates is the credential itself.

Headers

Idempotency-Key
string
required

A unique key per logical write. Replaying a request with the same key returns the first response byte for byte instead of applying the write twice.

Body

application/json

is_default is refused BY NAME: accepting it would silently re-point every price list and region that resolves against "the store's default currency" without touching a row either of those resources own, the same re-denomination hazard write_regions' currency_code carries. The FIRST currency a store ever adds becomes its default automatically, which is not a choice this route makes and so is not refused.

currency_code
string
required

A known ISO 4217 code, case-insensitive.

Response

Created

data
object