Guide
Server-to-Server Integration
Use the credential and scope intended for the trusted server operation.
Separate API identities
An approved partner uses a scoped partner Bearer key for external fulfillment. Developer operations use the developer account and permission model. Product licensing uses the product contract. These credentials are not interchangeable.
Keep partner secrets and developer tokens on trusted servers. Apply the endpoint's idempotency, product scope, response/error contract, and rate limit. A custom client does not gain broader permission by routing through a server.
External transactions stay explicit
Reporting an outside sale can establish the agreed product access without making SoundSync the seller of that transaction. Preserve external order and line references, reconcile retries, and handle relevant refunds through the supported model.