Authentication
Unless an endpoint says otherwise, every request requires a JWT bearer token issued by the Identity service:POST /auth/sign-in (which takes your API client credentials as HTTP Basic instead), service health checks (GET /health), and the hosted checkout pages for payment links.
Some sensitive operations also require the user’s transaction PIN in a pin header — see Authentication in the introduction.
Pagination
List endpoints return one page at a time:items plus a next cursor that is null on the last page. See Pagination.
Tenancy
Endpoints whose path starts with/realms/{realmId}/organizations/{organizationId}/ are tenant-scoped: the token you send must belong to that realm and be entitled to that organization. Your IDs are provided during onboarding.
Services
Not sure where to start? Billing manages the agreement and invoice lifecycle between you and your counterparties; Payment Links & Checkout is for collecting one-off payments through a hosted page; Banking is where money actually moves (PIX, boleto, wallets, cards).