Authenticate to the LineLeader Enroll API using JWT plus refresh-token flow for a long-running integration
domain: apidocs.childcarecrm.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Create a dedicated Service Account for the integration rather than reusing a human staff login
Exchange service account credentials for a JWT, which LineLeader documents as valid for 1 hour
Store the accompanying refresh token, valid for up to 72 hours, to mint new JWTs without re-authenticating from scratch
Build token-refresh logic that requests a new JWT before the 1-hour expiry using the refresh token
Re-run the full credential exchange once the 72-hour refresh-token window lapses
Known gotchas
The 1-hour JWT lifetime is short relative to typical batch-sync jobs, so integrations without proactive refresh logic will see intermittent 401s mid-run
The refresh token itself expires after 72 hours, so a service that goes offline over a long weekend can come back to a fully expired credential chain requiring re-authentication, not just a refresh
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?