Playbook Connect App
SEO Tools
Website Creation
Marketing Automation
Raise Money
Interactive Scheduling
Communication Tools
Financial Reporting & Payments
Camps
Clubs
Leagues
Schools
Facilities
Why We Do It
Our Clients
Our Mission
Events
Free Scheduler
Help Center
Knowledge
Contact Us
Job Description Generator
Logo Generator
Waiver Generator
Flyer Generator
Social Media Post Generator
Developers
An open, documented API for sports facility data
Registrations, participants, programs, schedules, rosters and payments, through a REST API and an MCP server. Published pricing, published limits, no gated portal.
MCP server
Your facility's data, available to AI agents
Playbook runs a Model Context Protocol server alongside the REST API. Any MCP-compatible agent or assistant can read and act on your registrations, schedules, rosters and payments using the same credentials and the same permissions as your API access.
Few sports platforms offer one. If you're building agent workflows for your front desk, coaching staff or parents, start here.
- Same data model and credentials as the REST API
- Tool calls billed at the same rate as API calls, nothing extra
- Sandbox environment for testing, free and uncounted
- Access logs available for your own activity on request
- Scoped to your organization's data only
What you can build
Built on your data, not ours
Everything in the API is your organization's own data. Here's what teams are building with it.
Parent-facing apps
Custom registration flows, schedule views and payment status inside your own branded app or site.
Athlete profiles and performance
Combine roster and participation data with your own performance tracking to build athlete histories.
Internal dashboards
Pull registrations, revenue and utilization into the reporting tools your staff already use.
AI agents via MCP
Let an assistant answer "who's on the 4pm roster" or "which programs are under-enrolled" against live data.
Pricing
Published rates, no sales call required
Most platforms meter API access and hide the rate behind a login. Ours is below.
| Item | Rate | Notes |
|---|---|---|
| Included allowance | 50,000 calls / month | No charge |
| Additional calls | $0.0015 / call | Invoiced monthly |
| MCP tool calls | $0.0015 / call | Same rate as API calls |
| Webhooks | Free | Not counted or billed |
| Sandbox | Free | Not counted or billed |
3,600 requests per hour, with a burst allowance of 100 per 10 seconds. Approaching a limit in normal use? We raise it rather than throttle. Full detail in the documentation.
Built with you
If the endpoint doesn't exist, we build it
Tell us what you need
Partners regularly need data or actions the API doesn't expose yet. Send us the use case and we'll scope the endpoint with you, not around you.
- Direct line to the engineers who own the API
- Sandbox access while we build
Change without surprises
Breaking changes carry at least 90 days' notice with the prior version supported throughout. Deprecations carry 180 days' notice with a replacement path.
- Versioned endpoints and a public changelog
- Non-breaking additions ship as they're ready
Request access
Get credentials
Tell us what you're building. We issue sandbox credentials first, production once you're ready. Requests go to api@callplaybook.com.