Build your own
music distribution panel.

The AATISTIC White Label API lets an authorized partner connect a separate music distribution panel to AATISTIC. Requests are authenticated using a partner API key, and release ownership is validated by the API.

Send the API key in the HTTP Authorization header using the Bearer scheme. Do not send it as a URL query parameter.

Authorization: Bearer YOUR_API_KEY
Accept: application/json

cURL example

curl -H 'Authorization: Bearer YOUR_API_KEY' \\
     -H 'Accept: application/json' \\
     'https://monthly.aatistic.com/api/api-releases.php'

The HTTP method shown for release-status.php reflects the supplied PHP code, which accepts the ID from either GET or POST. The three PDF endpoints are documented as listed in the PDF.

Send a multipart/form-data request. Artwork is uploaded as artwork. Track metadata uses array fields; audio files use individually indexed field names such as audio_1, audio_2.

Minimal cURL example

curl -X POST 'https://monthly.aatistic.com/api/api-release-upload.php' \\
  -H 'Authorization: Bearer YOUR_API_KEY' \\
  -F 'title=Example Single' \\
  -F 'release_type=Single' \\
  -F 'release_date=2026-11-01' \\
  -F 'label_name=Example Label' \\
  -F 'artwork=@cover.jpg' \\
  -F 'track_title[]=Example Track' \\
  -F 'genre[]=Pop' \\
  -F 'language[]=English' \\
  -F 'audio_1=@track.wav'

Successful upload response

{
  "success": true,
  "message": "Release uploaded successfully.",
  "release_id": 52,
  "user_id": 7,
  "white_label_id": "Example-Label",
  "status": "pending",
  "white_label_status": "Pushed"
}

Release fields

Track fields (array notation)

Audio field mapping

audio_1 = track-one.wav
audio_2 = track-two.mp3
audio_3 = track-three.wav

Multiple artists on a track

Use indexed artist arrays so each track can have its own primary and featured artists.

tracks_artist[1][]=Hudaif
tracks_artist[1][]=Ayaan
tracks_artist_role[1][]=Primary
tracks_artist_role[1][]=Feature

tracks_artist[2][]=John
tracks_artist_role[2][]=Primary

Release artist fields

Returns releases available to the authenticated partner. The PDF specifies this endpoint for refreshing the partner's release list when the page opens.

{
  "success": true,
  "releases": [
    {
      "release_id": 52,
      "title": "Testing EP",
      "artwork": "uploads/artwork/abc.jpg",
      "release_date": "2026-09-20",
      "tracks": 3,
      "primary_artist": "Hudaif",
      "status": "approved",
      "white_label_status": "Delivered"
    }
  ]
}

Fetch details for one remote AATISTIC release. The PDF shows the release ID in the id query parameter.

{
  "success": true,
  "release": {
    "title": "Testing EP",
    "release_date": "2026-09-20",
    "status": "approved",
    "artwork": "uploads/artwork/abc.jpg",
    "upc": "123456789012",
    "tracks": [
      {
        "title": "Alone",
        "isrc": "INAAA2600001",
        "genre": "Pop",
        "language": "English",
        "composer": "John",
        "lyricist": "Smith",
        "producer": "Mike",
        "explicit": "No",
        "content_id": "Yes",
        "clip_time": "00:45"
      }
    ],
    "artists": [
      {"name":"Hudaif","role":"Primary","spotify":"...","apple":"...","instagram":"..."}
    ]
  }
}

The supplied custom release-status.php reads release_id from the query string or POST body and returns the current status, rejection reason, release date, creation date, white-label ID, and push status.

{
  "success": true,
  "release": {
    "id": 52,
    "title": "Testing EP",
    "status": "approved",
    "reject_reason": null,
    "release_date": "2026-09-20",
    "created_at": "2026-09-10 12:00:00",
    "white_label_id": "Example-Label",
    "push_status": "Delivered"
  }
}

Partner-side status sync pattern

1. Store the remote ID. Save the AATISTIC release_id in your local release row after upload.
2. Authenticate server-side. Make the status request from PHP using Authorization: Bearer YOUR_API_KEY.
3. Fetch when the page opens. Query each local release that has a remote AATISTIC ID.
4. Display remote values. Use release.status and release.push_status; show reject_reason when present.
5. Fallback safely. If the remote API fails, show a clearly identified cached/local status rather than treating the fallback as live.

Release status

White Label / delivery status

Treat the release status and white-label delivery status as two separate values. A release may be approved while distribution delivery is still processing.

• Store the API key in server-side configuration or environment variables. Do not print it to the browser.
• Send the Bearer token over HTTPS for every API request.
• Do not trust a client-supplied remote release ID without checking that it belongs to the logged-in user in your local database.
• Keep your website's local users.id and local releases.user_id separate from the remote AATISTIC user ID.
• In the current ROVM integration, the remote AATISTIC upload is intended to use user_id = 853. This is a custom integration rule, not a standard field described in the supplied PDF.
• The API key row must be configured for the intended AATISTIC account and white-label permissions. Never alter a key hash manually to change account routing.

1. Configure API credentials. Confirm the API key is active, stored server-side, and mapped to the intended white-label account.
2. Implement upload. Send release metadata as multipart form data, artwork as artwork, track arrays in order, and audio as audio_N.
3. Store the remote release ID. Persist the AATISTIC release_id separately from your local primary key.
4. Build My Releases. Use GET /api/api-releases.php as documented in the PDF; refresh on page load for current status.
5. Build Release Details. Use GET /api/api-release-details.php?id=REMOTE_ID for track and artist details.
6. Test status and errors. Verify pending, approved, rejected, resubmitted, push statuses, invalid key, and release-not-found cases.
7. Protect secrets and logs. Do not display API keys or full Authorization headers in error output or logs.

Documentation version 1.0 · Prepared 06 Oct 2026 · Base URL: https://monthly.aatistic.com/api/