1. For business owners
You do not need to write code to understand how DING OS works with an AI assistant. Three concepts keep your operations safe:
API is the locked door
The public API (api.getding.io/v1) defines exact endpoints for reading bookings, shifts, inbox threads, and KPIs — nothing opens without a valid credential.
MCP is the instruction manual
Model Context Protocol (mcp.getding.io) gives AI tools a structured menu of actions and parameters so the assistant knows what it is allowed to read or trigger.
You keep the key
You generate, scope, and revoke API keys inside Workspace Settings. Remove a key once and external AI access stops immediately.
Practical workflows you can enable
Inspect closed shifts missing handover notes and automatically create a follow-up task on the team board.
Summarize inbound guest messages and prepare policy-grounded reply drafts for staff approval.
Read revenue, pacing, and key-result progress directly into executive summaries.
Autonomous AI campaign scheduling and cross-channel social auto-publishing.
- Create one dedicated key per tool so you can audit and revoke each integration independently.
- Apply least privilege: start with read-only permissions for reporting assistants before granting write scopes.
- Verify new prompts and scripts in a demo or test workspace before running against live guest operations.
2. For developers
Integrate Claude, ChatGPT, internal agents, or scheduled workers using standard HTTP REST or remote MCP.
https://mcp.getding.io
Append ?mode=readonly or assign read-only scopes when connecting reporting and audit assistants.
https://api.getding.io/v1/
Django routes expect a trailing slash on REST endpoints (for example /v1/bookings/ or /v1/shifts/).
How to issue a scoped workspace key
- Open Domains & API Keys in your workspace settings (/settings/domains?tab=keys).
- Choose the target workspace, set a descriptive label, and select read-only or specific write scopes.
- Copy the secret once into your password manager or environment variables — keys are never shown again after creation.
curl -sS https://api.getding.io/v1/shifts/ \ -H "Authorization: Bearer <WORKSPACE_SCOPED_KEY>"