API Docs for the enterprise endpoint

We have a separate endpoint that handles large files. You can send hours-long or even days-long audio to this endpoint

How the requests are counted

Basically, as 1 request per 18 seconds of audio.

When you upload a file, our servers think of it as a bunch of 18 seconds long audio chunks. If you don't want every one of these chunks to be recognized and counted as the requests, there are two parameters that you can use: skip and every.

  • skip - how many 18 seconds long audio chunks are skipped after the ones that are recognized.
  • every - how many chunks should be recognized in a row.

So if you want to recognize 18 seconds, then skip 54 seconds, then recognize 18 seconds again, skip 54 seconds again, etc., these parameters should be skip=3 and every=1. If you want to skip 108 seconds instead so it counts as 1 request per 126 seconds of audio, send skip=6 and every=1.

Where to get a token

You can get a token from our API Dashboard. Sign up with a Telegram account to get the first 300 requests for free.

We have different monthly subscription options starting from $2 per 1000 requests. We use Stripe for secure payments.

How to send files

There are two ways of sending files to the API:

  • Provide a URL of the file. Our server will download and recognize the file. Send the URL in the url parameter.
  • Post the file using multipart/form-data in the usual way the files are uploaded via the browser. Send the file in the file parameter, by POST. Useful if the file is not available by a URL.

You can try to send a file from a browser here (or here for csv results instead of json).

post
Send a file

https://enterprise.audd.io/
Form Data Parameters
api_token
REQUIRED
string
The token received from the Dashboard
url
POSSIBLY REQUIRED
string
The URL of the file for the recognition
file
POSSIBLY REQUIRED
binary
The file for the recognition
skip
OPTIONAL
integer
How many 18 seconds chunks are skipped after the ones that are recognized
every
OPTIONAL
integer
How many chunks should be recognized in a row
accurate_offsets
OPTIONAL
string
Set to "true" for getting accurate start and end offsets of the recognized tracks

How to get additional metadata, e.g. ISRCs and UPCs

You don't have to have an enterprise account in order to use the enterprise endpoint. But you need an enterprise account to get ISRCs and UPCs with the results. Let us know if you want access to these features: send an email to [email protected].