All requests to the Scheduler API must include an API key in theDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/greenmartialarts/shift-scheduler-web/llms.txt
Use this file to discover all available pages before exploring further.
Authorization header. The API uses stateless HMAC-signed keys — no session tokens or cookies are involved.
API key format
Keys follow a two-part format:user_id identifies your account. The signature is an HMAC hash that the API verifies on every request. Both parts are required — passing only a user ID will result in a 401 error.
Passing your key
Include the key in theAuthorization header of every request:
Requesting an API key
API keys are issued on request. Email the following address with your name and a brief description of your use case: arnav.shah.2k10@gmail.com You will receive your[user_id].[signature] key by email.
Error responses
| Status | Meaning |
|---|---|
401 Unauthorized | The HMAC signature is invalid, the key is malformed, or the key has been revoked. |
401, verify that:
- You are passing the full
[user_id].[signature]key, not just one part. - You have not trimmed or modified the signature.
- Your key has not been revoked (contact arnav.shah.2k10@gmail.com to reissue).
Rate limiting
Each API key has a daily quota. To check your current usage and remaining quota, callGET /api/usage.