District Resolve API Documentation
API-first surfaces for the web app, future mobile app, Chrome extension, district integrations, webhooks, and opt-in AI workflows.
Authentication
Use Auth.js sessions for web clients or scoped bearer tokens created in the Developer Console.
POST /api/api-tokensPATCH /api/api-tokens/{id}/revokeMobile Readiness
Mobile clients can bootstrap tenant data, register push tokens, request upload intents, and open deep links.
GET /api/mobile/bootstrapPOST /api/mobile/push-tokensPOST /api/mobile/deep-linkWebhooks
Signed event endpoints include delivery history and retry-ready tracking for integration teams.
GET /api/webhooksPOST /api/webhooks/{id}/testGET /api/webhooks/{id}/deliveriesPOST /api/webhooks/{id}/retryAI Ready
Organizations can opt in to AI features and dry-run smart triage before connecting a provider.
GET /api/ai/settingsPOST /api/ai/settingsPOST /api/ai/triage-previewVersioned API Access
District Resolve exposes canonical endpoints under /api/* and a compatibility layer under /api/v1/*. The v1 layer preserves request methods with a 307 redirect to the canonical route, which keeps mobile and extension clients stable while the web app evolves.
curl -H "Authorization: Bearer <token>" \ https://districtresolve.example/api/v1/mobile/bootstrap