Set the jurisdiction a tax rate applies in
Authorizations
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
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.
Path Parameters
Body
A PUT with every key required, because the three fields are ONE setting rather than three: a partial write leaves a rate bound to a jurisdiction the caller no longer meant, and the resolver keeps applying it there. The response is the WHOLE rate, identical to GET /api/v1/tax-rates/{taxRateId}.
A tax region in THIS store, from /api/v1/tax-regions. Null clears the link and widens the rate from one jurisdiction to the whole store. An id from another store is refused: the foreign key alone would not catch it.
An optional short merchant label ("GST", "VAT-RED"), or null to clear it. Opaque text with no schema and no enum: it is not a code from any tax standard.
Required. True means this rate STACKS additively on other matching rates; false means it OVERRIDES them. It is not defaulted, because defaulting it would change what the merchant charges on a key the caller never sent.
Response
Success
