Skip to main content
AudioShake is migrating all customers to the Tasks API. This page is provided for reference only. New integrations should use the Tasks API.
The legacy API is hosted at https://groovy.audioshake.ai and uses a Jobs-based model where one job processes one model against one audio file. If you are starting a new integration, use the Tasks API instead.

Authentication

All requests require a Bearer token in the Authorization header.
Contact support@audioshake.ai to obtain a legacy API token. Never store tokens in client-side code. If a token is compromised, contact support to invalidate it immediately.

Upload a file

Before creating a job, upload your audio file to receive an asset ID.

Upload from disk

Upload from URL

Upload response

Save the id — you will use it as assetId when creating a job.

Create a job

Each job runs one model against one asset. The model name and output format are specified inside the metadata object.
To process multiple models (for example, vocals + instrumental + drums), submit a separate job for each.

Job request fields

Job response

Save the job.id to poll for status.

Check job status

When status is completed, the response includes an outputAssets array with download links.

Music detection

The music_detection model returns a JSON array of time ranges where music is present.
Output format:
Confidence values closer to 1 indicate higher certainty that music is present.

Check usage

Returns the last 3 months of usage:

Migrating to the Tasks API

See Migrating from Jobs for a step-by-step guide.