Client area

GET · Billing & invoices

One billing address with its contacts

One billing address with its contacts

GET /api/v1/billing-addresses/{billingAddress}
R Read
Scope read:billing

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 the profile fields, currency, phoneNumber and contacts[]. Change it with manage_billing_addresses (action=update / set-primary / delete).

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.

401 No token was presented, or the token is revoked, expired or unknown.
403 The token lacks a required scope, or this account does not own the resource.
404 No such resource for this account.
422 Validation error
429 The rate limit for this token is exhausted. See `Retry-After`.
500 Something went wrong on our side. The failure is logged against `requestId`.
Esc
navigate open Esc close