Skip to main content
This walks through one end-to-end call against the Reporting API. By the end you’ll have a real response in your terminal and know where to go for everything else.

Prerequisites

  • A Monterey API key scoped to at least one organization.
  • A way to make an HTTPS request: curl, an HTTP client library, or any tool that can send an Authorization header.

1. Send your API key

Every request carries the same Authorization header — your API key, prefixed with Bearer:
The plaintext key is shown once when it’s minted. Store it like a password — only its hash is kept server-side, and a revoked key cannot be recovered.

2. Make your first call

Cash Receipts (/reports/crr) returns one row per payment within a date range. Pick a small from/to window for your first call:

3. Read the response

A successful call returns 200 with an items array. Each row carries the organization it belongs to so multi-org keys can group their own results:
An empty range returns 200 with {"items": []} — that is not the same as a 403. See Authentication for the full 401 / 403 split.

Authentication

Org-scoped keys, key rotation, what’s logged on every request.

Conventions

Dates, money in cents, the organization_id parameter, error shapes.

All endpoints

The full API surface — reports, resource endpoints, and payment operations.