Overview

The DJfindr API has two parts. The Public API publishes the DJfindr catalog for any application to read. The Management API acts on behalf of a signed-in person, as a client or as a DJ, within their own DJfindr account.

	Public API	Management API
Use it to	Search DJs and display profiles, mixes, posts, live events, reviews and reference data.	Read and change one person's bookings, payments, calendar, profile, content, messages and files.
Base path	`https://api.djfindr.com/prod/v1/public`	`https://api.djfindr.com/prod/v1/me`
Authentication	API key (`catalog:read`)	Sign in with DJfindr (OAuth 2.1)
Access	Read-only	Read and write, limited to the scopes the person approved
Rate limit	100 requests per minute per key	100 requests per minute per person and app
Reference	Public API	Account, Bookings, Payments, Messaging, Calendar, Profile and Content, Files, Webhooks

Both parts share the conventions described in Getting Started: the response envelope, pagination, errors, rate limits, prefixed ids and amounts in minor units.

Public API

The Public API is the catalog that djfindr.com displays. It is suited to marketplaces, venue and event sites, planning tools and any page that recommends or lists DJs.

Resource	Endpoints	Description
DJs	`GET /public/djs`, `GET /public/djs/{id_or_slug}`	Search with filters (genre, occasion, location, rate, rating, availability on a date) and retrieve a full profile.
DJ content	`GET /public/djs/{id_or_slug}/mixes`, `/posts`, `/live-events`, `/reviews`	A DJ's published mixes, posts, live events and reviews.
Reference data	`GET /public/occasions`, `/genres`, `/extras`, `/requisites`, `/profile-tags`, `/locations`	The vocabularies used across the catalog, each with a list and a retrieve endpoint.

curl "https://api.djfindr.com/prod/v1/public/djs?occasion=wedding&place_key=NY&available_on=2026-12-31" \
  -H "Authorization: Bearer djf_live_..."

📘
Attribution
The Public API is free on every plan. API keys are made in the developer portal, by any developer, DJ or client account. Show a Powered by DJfindr link wherever you display catalog data; the portal provides the snippet.

Management API

The Management API performs, on a person's behalf, what that person can do in their DJfindr account. Every path is relative to the signed-in person (/me/...), so a request never names an account: the access token identifies it.

Register your application as an app in the developer portal to get its client_id (see Register an app). Client accounts can always connect it; a DJ connects a third-party app on the Platinum plan.

Area	What it covers
Account	The signed-in person, their account and plan, the updates feed, search over their records, analytics and connected integrations.
Bookings	Requests and offers (proposals), offer documents, extensions, events, invitations, clients, reviews and booking settings.
Payments	Payments made and received, payouts, PayLinks and action links.
Messaging	Conversations and messages.
Calendar	Availability, busy blocks and the calendar feed.
Profile and Content	A DJ's profile, mixes, posts, live events and widget domains.
Files	Uploads, in one request or in parts.
Webhooks	Your application's webhook and its delivery log.

What stays on DJfindr

Some actions are completed only by the person on DJfindr, never by an application.

Action	How your application handles it
Accepting an offer, signing its documents and paying; paying a balance or an extension; cancelling a paid booking; a DJ's refund	Create an action link and send it to the person, who completes the action on DJfindr.
Saving a payment method, payout onboarding, plan changes, identity verification, closing the account	Direct the person to DJfindr. These are not available through the API.
API keys and apps	Made in the developer portal. These are not available through the API.
Calls, typing indicators and voice notes	Available in the DJfindr apps only.

Booking lifecycle

The following sequence shows a booking from the first message to a confirmed event. Each step appears in both parties' updates feed and, if your application registered one, its webhook.

Step	Party	Request
1. Connect your application	Either	Sign in with DJfindr, then `GET /me`
2. Contact the DJ	Client	`POST /me/conversations`, then `POST /me/conversations/{id}/messages`
3. Validate the request	Client	`POST /me/bookings/requests?dry_run=true`
4. Send the request	Client	`POST /me/bookings/requests` with an `Idempotency-Key`
5. Accept the request	DJ	`POST /me/bookings/proposals/{id}/accept-request`
6. Build the offer	DJ	`PUT /me/bookings/proposals/{id}/offer`, `POST /me/bookings/proposals/{id}/documents`
7. Send the offer	DJ	`POST /me/bookings/proposals/{id}/send-offer`
8. Check out	Client	`POST /me/bookings/proposals/{id}/checkout-link`; the client signs, accepts and pays on DJfindr
9. Confirm	Either	A `booking.confirmed` update (and `link.completed` for the application that created the link)
10. Pay the balance	Client	`POST /me/payments/{id}/pay-link`, when the booking was paid with a deposit

Guides

Guide	Covers
Sign in with DJfindr	OAuth endpoints, scopes, tokens, who can connect and API key access.
Responses and status codes	The `code` and `fields` keys, status codes and pagination.
Making changes	Request bodies, idempotency, concurrency control and dry runs.
Updates	The updates feed and its event types.
Webhooks	Registering a webhook, verifying signatures and handling retries.
Register an app	Registering an app in the developer portal: its type, redirect URIs, client secret, verification and who can connect it.
Action links	Links that a person opens on DJfindr to check out, pay, cancel, refund, upload or view a file.
Files	Uploading, importing and downloading files.
Messages	Conversations, message sequence numbers and sending rules.

The Management API is also available to AI assistants as tools of the DJfindr MCP server. See Connecting an AI Assistant.