Crunchtime Information Systems · Authentication Profile
Crunchtime Information Systems Authentication
Authentication
Crunchtime Inventory & Labor / Cruise APIs use custom header-based token authentication. Every request carries four headers: an access token plus the site name and an Application User's id and password. Tokens are minted per Application User in Enterprise Manager (Security > Application Users > API Tokens) and separate test and production tokens are issued. There is no OAuth2 or OpenID Connect surface, so this repo has no scopes/ artifact.
Crunchtime Information Systems secures its APIs with apiKey across 4 declared security schemes, as derived from its OpenAPI definitions.
CompanyRestaurantFood ServiceHospitalityInventory ManagementLabor SchedulingOperations ManagementBack OfficeSupply Chain
Methods: apiKey
Schemes: 4
OAuth flows:
API key in: header
Security Schemes
authenticationtoken apiKey
sitename apiKey
userid apiKey
password apiKey
Source
Authentication Profile
Work with this as data
Every security artifact here is available over the APIs.io API and to AI agents over MCP.