Overview

The ScheduleDrop API gives your backend machine-to-machine access to a single ScheduleDrop account. Your server holds the credential and calls this API; the customer's browser never sees it.

Everything runs as a customer submission

Not as the account owner the credential acts as. Terms of service are enforced, contacts are matched rather than rejected as duplicates, and admin-only fields and internal pricing are never returned.

Base URL

https://app.scheduledrop.com/api/v1

How it works

Create a credential in Settings → Application Settings → API Credentials.
Exchange it for an access token at the OAuth token endpoint. Tokens last 12 hours.
Read the booking form to learn which services, questions and fields the account expects.
Preview the price and availability, then create the booking.

curl -X POST https://app.scheduledrop.com/api/auth/oauth/token \
  -d grant_type=client_credentials \
  -d client_id=$SCHEDULEDROP_CLIENT_ID \
  -d client_secret=$SCHEDULEDROP_CLIENT_SECRET

curl https://app.scheduledrop.com/api/v1/booking-forms \
  -H "Authorization: Bearer $ACCESS_TOKEN"

Conventions

Pagination — list endpoints take cursor and limit (default 25, max 100) and return meta.next_cursor. The cursor is opaque; pass back what you were given.
Request ids — every response carries X-Request-Id. Send your own and it is echoed back. Quote it when reporting a failure.
Body size — requests over 1 MB are rejected with payload_too_large.

Authentication

Get an access token and keep it fresh.

Errors

The one error shape and every code it can carry.

Rate limits

600 reads and 60 writes a minute, per credential.

Booking forms

Start here — the form describes what to collect.