Reports API
The Reports API is the money side of SpaceMedia: royalty report intake, normalized analytics, exports, catalog mapping review, reconciliation, anomalies, disputes, and payout exceptions.
It is a separate product from the Delivery API, with its own host, its own credentials, its own release notes, and its own availability controls. Credentials are never interchangeable between the two.
How Reporting Works
Resource families, the two access surfaces, and integration principles.
Authentication
Machine OAuth versus human operational sessions.
Endpoint reference
Every operation, generated from the OpenAPI contract.
OpenAPI contract
Download the canonical spec for SDK generation and validation.
Before you integrate
- Confirm the route family you need is enabled in the target environment.
- Confirm your tenant is approved for that capability.
- Use machine OAuth only for operations that explicitly support it.
- Check the Reports API changelog before upgrading a client.
Full detail is in Availability.
Four rules for financial data
- Never parse an amount into a float. Keep decimal amounts as strings or arbitrary-precision decimals. Rounding errors in royalty data are expensive to unwind.
- Keep currency and period attached. An amount without its currency and reporting period is not a number you can reconcile.
- Treat a capability denial as unavailable, not broken. A feature-flag or tenant-policy denial is a configuration state, not a transient failure worth retrying.
- Tolerate unknown fields and values. Compatible additions can introduce new optional fields, enum values, and operations at any time.
The contract describes implemented behavior. Route publication, tenant approval, client scopes, and production sign-off are separate controls. Confirm all of them before depending on an operation in production.
Environment
The Reports API runs at https://reports.spacemedia.uk. Guarded routes stay unavailable until their deployment flag and tenant policy are enabled.
Was this page helpful?