API reference - PanoQore

The reference is generated from the panoqore.v1 protobuf contract and covers what an API key can call. Work that needs a person, such as approving a request, is in the console.

Categories

Category	Sections	What it covers
Core ledger	Accounts, Entries, Holds	The double-entry records everything else is built on.
Money products	Lending, Fees, FX, Named accounts	Lending, fees, FX and partner account numbers, on top of the ledger.
Finance operations	Reconciliation, Reporting, Approvals	Checking the ledger against partners, reporting on it, and reading what waits for approval.
Events and webhooks	Webhooks, Events	Being told when something changes, and reading the audit trail.
Tenant setup	Tenant, Chart of accounts, Identity	What this tenant has configured, and who is calling.

Trying a request

Each page has a playground. Enter your API key under Authorization. Use a test key: the playground sends real requests. Pick a server from the list at the top of the request. A write needs an Idempotency-Key, which can be any unique value.

Conventions


Authentication	`Authorization: Bearer pk_...`. See Authentication.
Writes	`Idempotency-Key` header. See Idempotency.
Bodies	`application/json`, `lowerCamelCase`. Zero values are left out of responses. See Money and data formats.
Lists	`page.size` and `page.cursor`. See Pagination.
Refusals	One envelope, with a stable code. See Errors.

Connect and gRPC

The same handlers also answer Connect and gRPC at /panoqore.v1.<Service>/<Method>, which is what the SDKs use. Refusals there carry the same code as a typed error detail.