Skip to main content
Every object has an id and an object field naming its type. Formats are described in Requests and responses.
Money fields are decimal strings with four decimal places. Timestamps are ISO 8601 in UTC. Calendar dates are YYYY-MM-DD in the subscription’s timezone.

Organisation

The organisation the API key belongs to. Retrieve it.

Customer

A customer, synced from a Xero contact. Endpoints.
A customer with no code can’t be found by customer_code. Give the customer a code before your integration needs to look them up.

Plan

A pricing plan. Endpoints. For how each type prices, see Plans explained.

Plan types

Tier

Plan meter

A meter a plan bills for, and how. A plan can bill any number of meters. Usage is billed in arrears, when the subscription’s period ends. See Usage-based billing.

Charge

A one-off fee that can be added to a new subscription. It bills once and doesn’t recur. Endpoints.

Subscription

A customer’s subscription to a plan. Endpoints. For the lifecycle, see Subscriptions explained.

Subscription meter

One entry in a subscription’s meters, for each meter its plan bills.

Subscription status

A subscription set to end at period end stays active with cancel_at_period_end: true until its end date.

Invoice

An invoice raised in Xero. Endpoints. Invoices are read-only in the API.

Invoice status

Xero sync

Invoice line

On a subscription created through the API, a charge takes the subscription’s discount only when you set apply_discount to true on that charge.

Usage event batch

What POST /v1/usage_events returns: how each event in the request fared. See Usage-based billing.

Usage event result


Credit note

A credit note raised in Xero, such as when a volume plan’s units cross into a cheaper tier or a reduction in units is credited. Endpoints. Credit notes are read-only in the API.

Allocation status

Credit note line

Allocation

A reverted allocation no longer counts towards remaining_credit.