The DJfindr API uses bearer tokens to authenticate requests. Tokens look like
djf_sk_ followed by 32 characters.
Authorization: Bearer djf_sk_...Obtaining access
| API Type | How to obtain access |
|---|---|
| Public API | If you are looking to access the DJfindr Public API, a token can be obtained from the DJfindr for Developers dashboard. Create an account with your email, provide us a few basic details, then create a token. The Public API is free to use with attribution wherever you show catalog data; the dashboard has copyable snippets. |
| Management API | If you are looking to access the DJfindr Management API, a token can be obtained from the integrations tab in Dashboard > Settings. |
Regardless of the API you are using, your token is shown once, when it is created, and is stored only as a hash afterwards. Neither we nor you can recover the value later — if you lose it, rotate it from the dashboard and you'll get a new one under the same label.
Treat the token as a secret. Do not embed it in client-side code or a mobile
app, where anyone can read it out of the bundle; keep it server-side, in your
platform's secrets store or an environment variable, and have your server call
the API on your users' behalf.
Make all requests over HTTPS. Requests without a valid token fail with 401.
curl https://api.djfindr.com/prod/v1/public/djs?occasion=wedding \
-H "Authorization: Bearer djf_sk_..."Why a request is refused
A 401 means the token was missing, unrecognised, or has been disabled. The
response is identical in all three cases, deliberately — an unauthenticated
caller learns nothing about which one applies.
A 403 means the token is valid but not permitted on that part of the API.
You will only see this if you hold a token for a DJfindr account tree and call
it against the wrong one; a public token never encounters it.