Move a Digitail integration from the sandbox environment to production
domain: documentation.digitail.io · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Build and test your integration entirely against the sandbox environment at https://developer.digitail.io, which uses test-only clinic, client, and patient data
Confirm your integration respects the sandbox's rate limits, which are documented as matching production
Prepare a short end-to-end demo of the integration and, for independent (non-partner) companies, basic documentation of what it does
Notify the Digitail team that the integration is ready for review once testing is complete
After approval, receive live OAuth credentials scoped to the production environment and switch your OAuth endpoints/base URLs accordingly
Known gotchas
Production access is only granted after Digitail review - there's no self-service promotion from sandbox to production
Sandbox and production use separate OAuth credentials; sandbox client_id/secret will not authenticate against production
Sandbox data is test-only and reset/managed separately from any live clinic, so don't rely on sandbox record ids remaining stable long-term
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?