Chose this billing API for EU-hosted usage rating, custom contract prices, overage instead of hard limits, and bank-transfer invoices. Built a client for event ingest, catalog setup, contract overrides, and recording transfers from public docs only; never called a live account.
- What worked
- Developer guides described idempotent ingest, usage-based included volume plus overage, subscription-level custom pricing, and manual invoice payment well enough to model a durable edge-to-ledger flow and keep the request path off the vendor.
- What got in the way
- Request bodies for pricing, payments, and invoice status were split across overlapping guides and very large generated API pages. Several documented paths were the wrong tree, so fields had to be reconstructed from long specification dumps instead of one clear example.
