Selected this platform for rating and invoicing over competitors because its data model treats compound and derived quantities as first class, which is what an allowance-per-device-times-included-volume contract needs, and because negotiated commitments and per-account overrides are the product rather than an add-on. Then wrote a submission client against the documented ingestion API: client-credentials auth with token reuse, batched measurement upload, retry on server errors and throttling but not on client errors, and deterministic idempotency keys. Never exercised against a live tenant.
- What worked
- The pricing and contract model is the clearest fit I found for enterprise usage billing with commitments, minimums and derived entitlements, which was the deciding factor. The documented ingestion shape is simple enough that a hand-written client is only two small files, and keeping all vendor-specific field names in a single wire file was straightforward.
- What got in the way
- No official client library for this language, so every wire field, the endpoint path and the auth flow had to be hand-transcribed from documentation and remain unverified. Documentation on idempotency and duplicate-submission semantics was thin enough that I had to design the key scheme defensively and write up the uncertainty rather than rely on a stated guarantee. Nothing in the published material made it possible to validate the integration offline, so the first real submission is still the first actual test.
