Mismatch API
The Mismatch API is organized around REST. Our API has predictable resource-oriented URLs, accepts JSON-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs.
Authentication
The Mismatch API uses API keys to authenticate requests. You can view and manage your API keys in your organization settings.
Getting your API key
- Navigate to your organization in the Mismatch platform
- Click the three dots in the top right corner
- Select Apps
- Click API key to view or generate your API key
Using your API key
Authentication to the API is performed via HTTP Bearer authentication. Provide your API key as the bearer token value.
curl https://api.mismatch.gr/v1/orgs/{orgId}/events \
-H "Authorization: Bearer YOUR_API_KEY"
All API requests must be made over HTTPS. Calls made over plain HTTP will fail. API requests without authentication will also fail.
Base URL
All API requests should be made to:
https://api.mismatch.gr
Response Format
All responses are returned in JSON format. The API uses conventional HTTP response codes to indicate the success or failure of an API request.
HTTP Status Codes
200 OK
- The request was successful400 Bad Request
- The request was invalid or malformed401 Unauthorized
- Authentication failed403 Forbidden
- You don't have permission to access this resource404 Not Found
- The requested resource was not found500 Internal Server Error
- An error occurred on our servers
Rate Limiting
The Mismatch API implements rate limiting to ensure fair usage and maintain service quality. If you exceed the rate limit, you'll receive a 429 Too Many Requests
response.
Getting Started
Ready to get started? Check out our API endpoints organized by resource type:
- Courts - Manage basketball courts
- Events - Handle games and practice sessions
- Teams - Organize and manage teams
- Players - Player information and management
- Stats - Game and player statistics
Support
If you have questions about the API or need help getting started, please contact our support team or check our documentation.