API | ID Crate

Everything the app does with links, tracked IDs, monitors and your library is available over a JSON API with a per-account key. Build a Discord bot that answers "ID?" with an answer, wire detection into your own tooling, or pull your crate into a spreadsheet.

Authentication

Create a key in Settings, then send it as a header. The key is shown once and only its hash is stored.

X-API-Key: mih_live_xxxxxxxx

Detect a track from a link

curl -X POST 'https://app.idcrate.co.uk/api/v1/detect' \
  -H 'X-API-Key: mih_live_xxx' -H 'Content-Type: application/json' \
  -d '{"url":"https://www.instagram.com/reel/xyz/"}'

# then poll until status is completed (usually 1 to 3 minutes)
curl 'https://app.idcrate.co.uk/api/v1/detect/123' -H 'X-API-Key: mih_live_xxx'

Start hunting an ID

curl -X POST 'https://app.idcrate.co.uk/api/v1/tracks' \
  -H 'X-API-Key: mih_live_xxx' -H 'Content-Type: application/json' \
  -d '{"artist_name":"KH","track_title":"Looking at Your Pager"}'

Is it in my library?

curl 'https://app.idcrate.co.uk/api/v1/library/match?artist=KH&title=Looking+at+Your+Pager' \
  -H 'X-API-Key: mih_live_xxx'

Endpoints

The full endpoint map is served by the API itself at app.idcrate.co.uk/api/v1: identity, library list and match, duplicates, tracked tracks with their matches, detections, and monitors with their results, plus the write endpoints for tracks, detections and monitors.

Limits