Get the tax rules
Your own tax rules (issue #341): the first rule whose country, region and business all match a customer decides what a new invoice bills them. Rules are tried in this order. Empty is a valid, intentional configuration: every invoice carries no tax until you add one.
apiKeyAuthorizationBearer <token>An API key from the Developers page. rhq_test_ keys reach the sandbox, rhq_live_ keys the live side.
Success
application/json- response
Success
data*array<>curl -X GET "https://example.com/v1/account/tax/rules"{ "data": [ { "country": "DE", "region": "Karnataka", "business": "required", "components": [ { "name": "VAT", "rateBps": 2000 } ], "reverseCharge": true } ]}Upload a customer portal logo POST
Stores an uploaded PNG, JPEG or WebP logo (at most 256 KB) and writes its own address onto the customer-portal builder’s draft `logoUrl` field (`logoDarkUrl` with `variant: "dark"`), seeding the rest of the draft from your live portal the first time it is ever written, same as `PATCH /account/portal/draft`. Paste a URL instead through that route for an SVG logo - there is no sanitizer here for one. `POST /account/portal/publish` copies the result onto your live portal, same as any other draft field.
Replace the tax rules PUT
Replaces the whole list, in the order they are tried. There is no id to patch one rule by: send every rule you want to keep. Turns the tax rules engine on for new invoices from now on, ahead of the older `defaultTaxBps`, even when sent empty.