Spend more time helping. Less time chasing messages.

Authorization: token with a private branch API key, configured by an administrator with Use and configure the API permission. Treat the key as branch-wide access. An account with enabled API integration is required; the reviewed docs do not specify a universal API plan surcharge. A fixed IP rate limit and a tighter write limit apply. Datetimes use UTC; send explicit timezone offsets when filtering a local day.

Administrator enables web services and REST, selects allowed functions in an external service and issues a user/service token with the required capabilities. Availability depends on the installed Moodle version, hosting configuration and administrator permissions. API documentation is also available inside the customer's own Moodle site; confirm its exact function schema there. Do not assume a managed hosting plan permits arbitrary external services.

Current API uses an organization-scoped X-Api-Key plus the account subdomain header and JSON:API headers. Generate approved keys in the Gingr admin dashboard. Legacy account-specific /api/v1 calls use a user-specific key and a different contract. Account/key permissions, configured services and location rules apply. Public docs do not establish a universal subscription entitlement or price; confirm these with Gingr. Do not mix current and legacy endpoints. Booking validation and any manual staff confirmation must be respected.

AuthX API key or JWT in an accepted bearer header, on a deployment where the administrator enabled that authentication flow. The user needs API authentication and entity/action permissions. A customer-controlled CiviCRM installation with supported APIv4 REST/AuthX configuration is required. Hosting, support or managed-service fees are separate; no universal SaaS plan entitlement is implied. Confirm the installation's entity fields and permissions in its API Explorer.