API reference group
Branding and Customer Library APIs
Product branding and proof-scoped customer access have different authorization requirements.
SoundSync
Supported route areas
| Method | Path | Responsibility |
|---|---|---|
| GET / POST | /api/license/branding | Product-scoped branding; no serial is required for the branding lookup |
| GET / POST | /api/license/v1/library-token | Issue the supported customer-library token using authorized customer/machine/session proof |
| GET / POST | /api/license/v1/webview-library | Resolve supported customer-library/WebView access for the authorized context |
Branding is not customer access
Branding uses the supported product credential/native-client context. It does not prove customer ownership or authorize a library. Generated local configuration is a snapshot unless that runtime explicitly refreshes the relevant values.
Library token and WebView routes use supported plugin/customer/session proof and still check the relevant access context. Do not substitute an arbitrary serial, customer ID, or developer session token to browse another customer's library.
Session and audio state differ
A customer portal session can expire independently of machine licensing. Refresh the supported browsing session without calling it a device deactivation. Keep returned tokens private and out of public screenshots.
Use the detailed customer-library reference for fields, responses, errors, and download permissions. The route map here does not invent a complete JSON fixture.