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
Legal
API Terms of Use
Version 1.0, effective September 1, 2026
These API Terms of Use ("API Terms") govern access to and use of the application programming interfaces, MCP server interfaces, developer tools and related documentation (together, the "API") made available by NYC Sports LLC d/b/a Playbook ("Playbook", "we", "us").
These API Terms apply in addition to the Playbook Terms and Conditions and to any signed agreement between Playbook and the organization accessing the API (a "Client"). Where a signed agreement conflicts with these API Terms, the signed agreement controls.
By requesting credentials or using the API, you accept these API Terms.
1Definitions #
- "Client Data"data originating from a Client's own operations and its relationships with its own customers.
- "Credentials"API keys, tokens, client secrets and any other authentication material issued by Playbook.
- "Documentation"the endpoint reference, schemas, rate limits and integration guides Playbook publishes at callplaybook.com/api-docs.
- "MCP Interfaces"Playbook's Model Context Protocol server endpoints and the tools exposed through them.
- "Platform"the Playbook software platform and services.
2Access #
2.1 Playbook grants each Client a non-exclusive, non-transferable, revocable right to access the API during the term of its agreement with Playbook, for the purpose of building and operating integrations and applications that work with that Client's own data.
2.2 Access is provided per environment. Production credentials are issued separately from sandbox credentials.
2.3 Playbook will work in good faith to build and expose the endpoints Clients need, including endpoints that do not exist today, and will share what it is legally and contractually able to share.
3Credentials #
3.1 Credentials are confidential and issued to a named Client. They may not be shared, sublicensed, resold or transferred outside the Client's organization.
3.2 Credentials must not be embedded in client-side code, mobile applications, public repositories or any location where they could be extracted by a third party.
3.3 Clients are responsible for all activity under their Credentials, and must notify Playbook promptly if they believe Credentials have been compromised.
3.4 Playbook may rotate or revoke Credentials where necessary to protect the Platform, with notice where practicable.
4Fees #
4.1 Allowance. Each Client receives 50,000 API calls per month at no charge.
4.2 Rate. Calls beyond the allowance are billed at $0.0015 per call, invoiced monthly.
4.3 MCP. MCP tool invocations are counted and billed on the same basis and at the same rate as API calls.
4.4 Webhooks. Webhook subscriptions and deliveries are not counted against the allowance and are not billed. Playbook encourages event-driven integration.
4.5 Sandbox. Sandbox and testing usage is not counted or billed.
4.6 Changes. Playbook may adjust published rates on sixty (60) days' written notice.
5Permitted Use #
Clients may use the API to:
- Read and write their own Client Data
- Build applications, dashboards, athlete profiles and internal data environments on top of the Platform
- Integrate the Platform with third-party tools the Client uses
- Automate their own operational workflows
6Rate Limits & Fair Use #
6.1 Published rate limits apply per endpoint and per Client and are set out in the Documentation. The current default is 3,600 requests per hour, with a burst allowance of 100 requests per 10 seconds. Higher limits are available on request.
6.2 Limits exist to protect Platform stability and performance for all Clients — not to restrict any Client's use. Where a Client approaches a limit in the normal course of business, Playbook will raise it where reasonably able rather than throttle. Requests go to api@callplaybook.com.
6.3 Playbook may throttle or temporarily suspend access where usage threatens Platform stability, with notice where practicable and restoration as soon as the issue is resolved.
6.4 Clients must not circumvent rate limits through multiple credential sets, distributed requests or similar means.
7Restrictions #
Clients must not:
7.1 Access, or attempt to access, data belonging to any other Playbook client.
7.2 Reverse-engineer, decompile or reconstruct the Platform's underlying database schema, data models or algorithms; or design, build or specify a database schema, data model or system architecture derived from, based upon, or substantially reflecting the Platform's schema, data architecture or data relationships, including as observed through the API, MCP interfaces, exported data structures or documentation.
7.2A Replicate, imitate or create any product incorporating the Platform's user interface designs, screen layouts, navigation structures, interaction patterns or visual design system — whether manually, automatically, or using generative or AI-assisted development tools.
7.3 Extract Playbook's model outputs, inference logs, or analytics aggregated across Playbook's client base.
7.4 Use data obtained through the API to train, fine-tune or evaluate machine learning models on data originating from other Playbook clients.
7.5 Resell, redistribute or provide API access to third parties, or operate the API as a service for others.
7.6 Access or use the API in order to build a competitive product or service, to build a product using similar ideas, features, functions or graphics of the Platform, or to copy any ideas, features, functions or graphics of the Platform. This mirrors, and does not replace, Section A3.1(c) of the Playbook Terms and Conditions.
7.7 Use data obtained through the API to develop, specify, benchmark or market any youth or recreational sports registration, enrollment, scheduling, roster management or payment processing product.
7.8 Share non-public API features, endpoints, schemas or Platform functionality with any third party.
7.9 Use the API in a way that violates applicable law, infringes third-party rights, or creates risk to the Platform or its users.
7.10 Remedy. Where Playbook reasonably suspects a breach of this §7, it may suspend API access without advance notice, in addition to any other remedy available to it.
8Data & Privacy #
8.1 Ownership. Clients own their Client Data. Playbook owns the Platform, its software, schema, models and algorithms. Clients grant Playbook the right to use data on the Platform to provide, operate, secure, support and improve the Platform and its services, including in aggregated and de-identified form.
8.2 Data concerning minors. A significant portion of data on the Platform concerns minors. Clients must handle it consistently with COPPA and applicable state privacy laws, apply data minimization, obtain any necessary parental or guardian consents, and retain identifying information no longer than needed for the purpose it was collected.
8.3 Client-submitted data. Clients are responsible for data they write into, upload to or transmit through the API — its accuracy, its legality, and their right to submit it. Playbook does not monitor or validate submitted data and is not responsible for it, but may remove or suspend access to anything it reasonably believes is unlawful, infringing or a risk to the Platform.
8.4 Feedback. Suggestions and ideas for improving or modifying the API or the Platform are not confidential. Clients grant Playbook a perpetual, irrevocable right to use them without compensation or attribution, consistent with Section A5.3 of the Playbook Terms and Conditions.
8.5 Aggregate data. Playbook may use, reproduce and exploit data with personally identifying information removed, consistent with Section A4.3 of the Playbook Terms and Conditions.
8.6 Sub-processing. Clients must not disclose data obtained through the API to third parties without Playbook's prior written consent, not to be unreasonably withheld. Consent is not required for a Client's own affiliates named in a signed agreement with Playbook.
9Security #
9.1 All API traffic must use TLS 1.2 or higher.
9.2 Clients must maintain reasonable administrative, technical and physical safeguards for data obtained through the API.
9.3 Each party will notify the other within seventy-two (72) hours of any confirmed security incident affecting data shared through the API.
9.4 Playbook logs API and MCP access. Access logs are available to a Client on request for that Client's own activity.
10Changes & Versioning #
10.1 Playbook publishes API versions and maintains a changelog in the Documentation.
10.2 Playbook will give at least ninety (90) days' notice before any breaking change to a published endpoint, and will support the prior version throughout that period.
10.3 Non-breaking changes — new endpoints, new optional fields, performance improvements — may be released without notice.
10.4 Playbook's data security and compliance policies will develop over time as regulation and industry standards do. Where a change materially affects a Client's access, Playbook will give reasonable notice and work with the Client on an alternative.
10.5 Playbook may deprecate an endpoint on one hundred eighty (180) days' notice, and will identify a replacement path where one exists.
11Availability & Support #
11.1 Playbook does not warrant uninterrupted API availability. Planned maintenance is announced in advance where practicable; status and incidents are published at the Playbook support site.
11.2 API support is provided through the Client's standard support channel. Where a Client has a signed agreement with a service level, that service level applies to the API on the same terms.
11.3 Where a signed agreement fixes these API Terms as of its effective date, that agreement controls and material changes will not apply to that Client without its written consent.
12Intellectual Property #
Playbook retains all right, title and interest in the API, the Platform, the Documentation, and all improvements — including improvements suggested by or developed in collaboration with a Client. Clients retain all right, title and interest in their own marks, content and Client Data. Nothing here grants either party any license except as expressly stated.
13Warranty Disclaimer #
The API is provided "as is." Playbook disclaims all warranties not expressly stated, including implied warranties of merchantability, fitness for a particular purpose and non-infringement. Data is provided as it exists on the Platform; Playbook does not warrant that it will be free of error, and is not liable for decisions made based on it.
14Liability #
Except for a Client's breach of §§3, 7 or 8, and except for either party's indemnification obligations, neither party's aggregate liability arising from API use exceeds the fees paid to Playbook in the twelve (12) months preceding the claim. Neither party is liable for consequential, incidental or punitive damages.
Where a Client has a signed agreement with Playbook containing a liability provision, that provision controls.
15Indemnification #
Clients will indemnify Playbook against claims arising from their use of the API, from data they submit, or from a security incident affecting API data in their custody. Playbook will indemnify Clients against claims that the API infringes third-party intellectual property rights.
16Suspension & Termination #
16.1 Playbook may suspend API access immediately where necessary to protect the Platform, prevent a security incident, or comply with law, with notice as soon as practicable.
16.2 Playbook may suspend access for material breach of these API Terms, with thirty (30) days to cure where the breach is curable.
16.3 API access ends when the Client's underlying agreement with Playbook ends.
16.4 On termination, Clients must cease API use, delete Credentials, and — on request — confirm deletion or return of data obtained through the API. §§7, 8, 12, 14 and 15 survive.
17Changes to These Terms #
Playbook may update these API Terms. Material changes take effect thirty (30) days after being published, with notice to Clients with active Credentials. Continued use after that date constitutes acceptance. Where a Client's signed agreement fixes these API Terms as of a given date, that agreement controls.
18Confidentiality & Trade Secrets #
Confidential Information includes the Platform's source code, database schema, data architecture, data models, API design, user interface designs, screen layouts, interaction flows, product roadmap and the technical know-how disclosed in the course of integration work. Each party acknowledges that this information derives independent economic value from not being generally known, that reasonable measures are taken to preserve its secrecy, and that it constitutes trade secrets under the Defend Trade Secrets Act, 18 U.S.C. § 1836 and applicable state law.
Each party will protect the other's Confidential Information with at least reasonable care, use it only for purposes of API access and integration, and disclose it only to personnel who need it and are bound by comparable obligations. This survives three (3) years, and indefinitely as to trade secrets. It does not apply to information that is public through no fault of the receiving party, independently developed, or required to be disclosed by law with prompt notice to the disclosing party.
19Change of Control #
Each party will notify the other within ten (10) business days of signing any agreement contemplating a change of control. Where a Client is acquired by a provider of youth or recreational sports management software, Playbook may terminate API access on notice, and §§7 and 8 survive for the remainder of the Client's underlying agreement term.
20Remedies #
20.1 Injunctive relief. The parties agree that breach of §§7 or 8 would cause irreparable harm for which monetary damages are inadequate, and that Playbook may seek injunctive relief without posting bond and without proving actual damages.
20.2 Liquidated damages. Given the difficulty of quantifying harm from misuse of Confidential Information, liquidated damages for breach of §§7.2, 7.6 or 7.7 will be the greater of (i) $100,000, or (ii) Playbook's documented development cost for the affected component. The parties agree this is a reasonable estimate of anticipated loss and not a penalty.
20.3 Disgorgement. The breaching party will additionally account for and pay over profits attributable to the breach.
20.4 Attorneys' fees. The prevailing party in any proceeding to enforce §§7, 8 or 20 recovers reasonable attorneys' fees and costs.
21Dispute Resolution #
21.1 Arbitration. Disputes will be submitted to binding arbitration in New Jersey before a single arbitrator with substantial experience in software and intellectual property disputes.
21.2 Discovery. Each party may request and receive production of documents relevant to the claims — including source code, database schemas, design files and development records, subject to a protective order — not fewer than four (4) depositions per side, and one (1) expert report per side. The arbitrator will permit inspection of source code and development history where misappropriation of Confidential Information is alleged.
21.3 Court carve-out. Either party may bring an action in court seeking injunctive relief, or asserting claims for infringement or misappropriation of intellectual property, without waiving arbitration of remaining claims.
21.4 Timeline. The arbitrator will schedule a hearing within one hundred eighty (180) days of appointment absent good cause.
22General #
Governed by the laws of the State of New Jersey. If any provision is unenforceable, the remainder continues in effect. These API Terms, together with the Playbook Terms and Conditions and any signed agreement, are the entire agreement on API use.
Questions: api@callplaybook.com
Legal notices: legal@callplaybook.com