Schedule Genius has a full REST API. Connect your ATS, push your roster in seconds, and pull schedule results into whatever tool your team already uses. No manual re-entry.
{
"team_id": "neurology-2025",
"participants": [
{ "name": "Dr. Amara Osei", "role": "faculty" },
{ "name": "Priya Ramirez", "role": "candidate" },
{ "name": "Marcus Chen", "role": "candidate" },
{ "name": "Lena Vasquez", "role": "faculty" },
{ "name": "James Park", "role": "candidate" }
// ...195 more
]
}
Your ATS has every candidate's name, email, and preferences. Typing it all into another tool isn't a workflow. It's a tax on your team's time, and a source of errors.
Push hundreds of participants in a single API call. The endpoint handles upserts, so the same request works for your initial import and every update after. New candidate? One line.
As your applicant list changes, your scheduling data changes with it. Run the sync as often as you need. The same request handles adds and updates without you having to track what changed.
What used to take an afternoon of copy-paste now happens in the background. Your coordinators spend their time on candidates, not on spreadsheet transfers.
Your interview pairs don't live in a dashboard. They belong in the systems your team already uses. Read them directly from the API and push them wherever they need to go.
Delegate access without delegating risk. Every API token is scoped at the team level, not the organization level.
Every API key is scoped to a specific team. The biochemistry program sees their events. The bioinformatics program sees theirs. Cross-program access isn't possible regardless of configuration.
After invitations go out, structural settings lock automatically. Business rules that protect your live program are enforced at every API call, regardless of which system is making it.
A standard REST API with a complete OpenAPI spec. If your team has built one integration before, this takes one afternoon.
Create a Schedule Genius account, navigate to your team settings, and generate a JWT token. It's scoped to your team and revocable at any time. Full interactive docs are available — import the spec into Postman or generate a typed client in your language of choice.
POST your participants via REST. The bulk endpoint handles upserts, so the same call works for your initial sync and every update after. Send 2 records or 2,000. The API validates and confirms what changed.
After the schedule runs, GET the pairs endpoint. You get a clean JSON array with each match: who meets who, when, and for how long. Pipe it to your calendar system, your notification tool, or your own database.
Write your integration once and trust it to keep working. Audit logging and rate limiting are built into the API. Validation too.
Each token is bound to exactly one team. An integration for one department cannot read or write another's data. No permission misconfiguration can cross that boundary.
The API handles burst traffic gracefully. Rate limit headers tell you exactly where you stand at every call. You won't accidentally flood your scheduling data during a peak import window.
Every write operation is logged: what changed, when, and which token did it. Useful during incident response, and useful during onboarding when you're still testing.
Machine-readable spec on every deployment. Browse the interactive explorer, import into Postman, or generate a typed client. Everything you need to get a working integration into code review by end of day.
Start with the API documentation, or book a call and we'll walk through your data pipeline together.