GET · Billing & invoices
List a billing address's contacts
List a billing address's contacts
/api/v1/billing-addresses/{billingAddress}/contacts
This scope is inferred from the method and the endpoint's group — the OpenAPI document does
not carry one per operation. The wire is authoritative; whoami reports what your
token actually holds.
Description
Returns {billingAddressId, data:[{id, type, email}]}. Add or remove one with manage_billing_address_contacts (action=add / action=remove).
Path parameters
| Name | Type | Description |
|---|---|---|
billingAddress
required
|
string |
Query parameters
| Name | Type | Description |
|---|---|---|
billing_address_id
required
|
integer | Minimum 1. |
Responses
The specification does not describe this response body; the note in the rail says what to expect.
Every non-2xx response is an RFC 7807 problem with a stable
code.
Commonly returned errors
The codes this operation reaches on its own path: the auth stack, its own validation and
ownership checks, and the transport. Not a closed set — a shared code from the
full registry can still surface. Each links to the code’s own page,
the same URL its type dereferences to.