CourtReserve API Overview

The CourtReserve API provides seamless access to a variety of features that enable smooth integration with external platforms, empowering organizations to extend their functionality and improve operational efficiency. Built for reliability and performance, the API supports only HTTPS requests and JSON data, ensuring secure communication.

Swagger API Documentation: https://api.courtreserve.com/swagger/ui/index

Organization API vs. Enterprise API

1. Organization API

   • Designed for managing data at individual locations.

   • Each location is assigned unique API keys, ensuring separate access for specific clubs or facilities.

   • Ideal for organizations that prefer localized control over their operations and need to manage data per location.

   • To enable the API in your organization, navigate to Settings -> Additional Features -> Integrations.

2. Enterprise API

   • Provides centralized access with a single set of API keys.

   • Offers a global view across all locations, making it perfect for organizations that need aggregated reporting and oversight.

   • Simplifies integration for enterprises managing multiple facilities under one umbrella.

   • To enable Enterprise API for your enterprise, contact customer success.

 

API Access Setup: Organization API and Enterprise API

Organizations must be under the Scale or Enterprise subscription plan to receive API access. API access is not available for organizations under the Start or Grow plan or those on legacy pricing. Organizations that have not switched to the new pricing model (introduced June 1, 2024) can request this update by speaking with our Customer Success team.

Authentication

The CourtReserve API uses Basic Authentication  to secure API access. To authenticate your API requests, include the API username and password provided during the API setup in the Authorization header of each request.

 

Rate Limiting

To ensure the stability and performance of the CourtReserve API, a rate limit has been enforced.

Rate Limit

• 60 requests per minute per API key.

Handling Rate Limits

1. If the limit is exceeded, the API will return an HTTP 429 Too Many Requests response.

2. The Retry-After header in the response indicates the number of seconds to wait before retrying.

Organization API Functionalities

The Organization API provides a comprehensive set of endpoints that allow administrators to manage memberships, members, families, events, reservations, and transactions. These services offer flexibility and control over the data and operations at individual locations.

Enterprise API Functionalities

The Enterprise API provides key reporting and management capabilities at the enterprise level. It allows organizations with multiple locations to retrieve aggregated data and insights across all associated locations, streamlining oversight and reporting.