API reference · Billing

Update the billing profile

Updates the billing profile.

puthttps://api.integrable.cloud/api/billing/profile

Authentication: Bearer token
Retries: Idempotency-Key
Body: application/json
Version: 2026-09-03

Changing this does not rewrite past receipts. Every issued receipt renders from the snapshot frozen onto its own payment row, so a corrected company name applies to future documents and leaves settled ones alone - which is the behaviour an auditor expects and the opposite of what a naive join would produce.

Headers

Idempotency-Keystring
A unique key of your choosing, so this request can be retried safely. The first request with a given key executes; every replay returns that first response unchanged, with Idempotent-Replay: true set.
Generate one key per action, not per session - reusing a key with a different body is refused with 422 rather than silently replaying the wrong answer. Keys are remembered for 24 hours. A request that failed releases its key, so a retry after fixing the payload runs normally.
Up to 255 characters

Request body

application/json · required

BillingProfileIn

address_line1string
Default: ·Up to 200 characters
address_line2string
Default: ·Up to 200 characters
billing_emailstring
Default: ·Up to 320 characters
citystring
Default: ·Up to 120 characters
country_codestring
Default: ·Up to 2 characters
legal_namestring
Default: ·Up to 200 characters
postal_codestring
Default: ·Up to 24 characters
state_codestring
Default: ·Up to 8 characters
tax_idstring
Default: ·Up to 64 characters
tax_id_typestring
Default: ·Up to 16 characters

Responses

200OKapplication/json
Message
- messagestringrequired
- okboolean
  Default: true
5 response headers
RateLimit-Limit
Requests permitted in the current window.
RateLimit-Remaining
Requests left in the current window. Back off before it reaches 0.
RateLimit-Reset
Seconds until the current window resets.
X-API-Version
The dated version of the API contract that served this response, e.g. 2026-09-03. Pin against it; it changes only when a response shape changes incompatibly.
X-Request-ID
Quote this in a support request to identify the call.
422Validation error
The shared error envelope, served as application/problem+json with error.code set to validation_error. Its details name each field that failed and why.

Example request

curl

curl -X PUT "https://api.integrable.cloud/api/billing/profile" \
  -H "Authorization: Bearer $INTEGRABLE_API_KEY" \
  -H "Idempotency-Key: $(uuidgen)" \
  -H "Content-Type: application/json" \
  -d '{
    "address_line1": ""
  }'

Set INTEGRABLE_API_KEY first. The same call from the TypeScript or Python SDK takes the same fields.

Example response

200 OK · application/json

{
  "message": "string",
  "ok": true
}

Generated from the schema above — the shape is exact, the values are placeholders.

Errors

Failures use one envelope on every endpoint, described in Retries, versioning and limits. The codes you are most likely to meet here:

validation_error · 422 — The payload was well-formed JSON but failed schema validation.
unauthenticated · 401 — The request carried no API key, or one the API could not verify.
forbidden · 403 — The key is valid, but it is not allowed to do this — either the scope is missing or the resource belongs to another workspace.
idempotency_key_reused · 422 — This `Idempotency-Key` was used before, for a request with a different body.
rate_limited · 429 — Too many requests in the current window. The limit is per workspace, and some endpoints add a per-bot limit on top.

More Billing endpoints

Something here wrong or missing? Tell us — the documentation and the API are maintained by the same person, so a correction is a fix rather than a ticket.