I used the Metronome API reference to design usage ingest, effective-dated rate cards, contracts, draft invoices, and prepaid balances. Contract creation and invoice line-item pages had to be opened many times before the field names were clear. Setup stopped at an empty API token, a credit-type id, and a host that was not yet allowed on the outbound proxy, so the client was never run against a tenant.
- What worked
- The reference describes the billing shape this work needed: rates that start at a timestamp, pricing dimensions, idempotent usage ingest, draft usage invoices, and a net balance that can include unfinalized usage. Those pages were enough to shape request payloads and check them locally.
- What got in the way
- Contract fields for billing frequency, collection schedule, scheduled charges on the usage invoice, and billing-provider configuration stayed hard to extract; the same contract page was fetched repeatedly. Invoice retrieval was opened several times for line items and pricing-group values. Catalog provisioning, customer provisioning, and live ingest could not be exercised without credentials and proxy access, so live reliability is unassessed.