Run distribution from your own product

Engine is the Aevora API. Create releases, deliver them to stores, read analytics and run royalties over REST, from the product your customers already use. The docs are public and there is a sandbox to build against.

Interface
REST and JSON
Authentication
API keys, one set per environment
Sandbox
Test deliveries, no stores involved

Four calls take a release from draft to statement

The API follows the path a release takes in the dashboard: create it, deliver it, read the numbers as they arrive, then read the statement. Pick a call to see what you send and what comes back.

  • Requests and responses are JSON
  • An error names the field that failed and why
  • The same calls work in the sandbox and in production

Engine API

Example requests

POST/v1/releases

Request body

{  "title": "Night Drive",  "artist": "Mira Kaya",  "label": "Northfield Audio",  "release_date": "2027-03-12"}

Response

{  "id": "rel_8f2k1",  "status": "draft",  "upc": null}

What sits around the endpoints

The calls are the short part of an integration. These are the parts that keep it working when nobody is watching.

Webhooks
Receive an event when a delivery changes state, a release goes live or a statement is ready, so you do not have to poll.
Idempotency keys
Send a key with a write request and a retry returns the first result instead of creating a second release.
Pagination
Lists return a cursor. Pass it back to get the next page, in the same order every time.
Sandbox
A separate environment with its own keys. Deliveries run from start to finish and stop before any store.
Versioning
The version is part of the path. A breaking change ships under a new version, so the one you built against stays as it is.
Rate limits
Each response tells you how much of your allowance is left, and a limited request tells you when to try again.

From first key to live delivery

  1. 1

    Get your keys

    Apply for an account. Once it is approved, create a sandbox key.

  2. 2

    Build against the sandbox

    Create releases and run test deliveries until your integration handles every state.

  3. 3

    Request production access

    Tell us what you are building. We review it and issue production keys.

  4. 4

    Deliver

    Switch to the production key and the same calls reach real stores.

Questions about Engine

No. The reference is public. You need an account, which we open by application, only when you want a key.

Yes. A release created over the API appears in the dashboard, and one created in the dashboard can be read and delivered over the API.

The delivery moves through the same states as a real one and sends the same webhooks, but nothing is sent to a store.

Make your first request in the sandbox