Sonentra API
Documentation

Getting Started

Sonentra is a server-to-server API platform. Your application owns its customer experience, artist onboarding and internal approval flow. Your backend uses Sonentra to create catalogue records, select destinations, submit releases and synchronize delivery results.

Base URL

https://sonentra.com/wp-json/sonentra/v1

Recommended flow

Authentication

Send the API key in the Authorization header for authenticated requests.

Authorization: Bearer sn_test_••••••••••••
Content-Type: application/json
Accept: application/json

Keep keys server-side. Never expose secret keys in frontend JavaScript, mobile app source code, screenshots or public repositories.

Sandbox & Production

Bearer sn_test_••••••••

Bearer sn_live_••••••••

Stores / DSP Catalogue

Build the store selector in your own platform from Sonentra's catalogue instead of hard-coding destinations.

Example response shape

{
  "success": true,
  "data": [
    {
      "code": "spotify",
      "name": "Spotify",
      "status": "available"
    }
  ]
}

Artists

Retrieve artists belonging to the authenticated client.

Create an artist record and retain the returned Sonentra artist identifier for release workflows.

Releases

Create the release container before attaching tracks, assets and DSP selections. Send only metadata fields supported by the current API schema.

Tracks & Assets

Add track metadata to the release. Audio/artwork requirements should follow the rules returned or documented by Sonentra for the current integration.

Select Stores

Example

{
  "stores": [
    "spotify",
    "apple-music",
    "audiomack",
    "boomplay"
  ]
}

Only submit store codes returned by the Sonentra Stores API for the authenticated account.

DSP Validation

Validate the release for a selected destination where validation is supported. Surface returned validation issues in your own platform and allow the operator to correct them before submission.

Submit Release

Submit only after your own internal approval is complete, required tracks/assets are attached, destinations are selected and validation issues are resolved.

Status & Deliveries

Use these endpoints to synchronize overall processing and DSP-level delivery results into your own dashboard. Display the exact states returned by Sonentra.

Webhooks

Register an HTTPS endpoint for supported Sonentra events. Process webhook events idempotently and log the event/result without exposing secrets.

Errors & Troubleshooting

Inspect both the HTTP status code and the returned JSON body. For request/authentication/validation problems, correct the request before retrying. For temporary server failures, retry safely and avoid duplicating non-idempotent operations.

Security

• Keep API keys in server-side environment variables or a secrets manager.
• Separate Sandbox and Production credentials.
• Use HTTPS for API and webhook traffic.
• Rotate exposed or compromised credentials immediately.
• Never log complete secret keys.
• Restrict Production keys to only the services that need them.

Production Checklist