Overview
Every route in the Specter API, grouped by area.
Loading documentation…
Every route, generated from the service's own action catalog — the same catalog Neo and the MCP server use, so the reference and the API cannot drift apart.
| Area | Covers |
|---|---|
| Board key routes | The two routes a board key opens |
| Boards and records | Boards, pages (Leads, Deals…), rows, columns, forms, lenders |
| Communications | Email, texts, threads, templates, blasts, notifications, calendar |
| Money | Accounting, payments, schedules, servicing, billing |
| Documents and files | Files, documents, requests, signing, Drive and OneDrive |
| Automation | Workflows, tasks, webhooks, integrations, reports |
| Workspace and account | Members, teams, settings, underwriting, API keys |
The board key routes take a board or page key. Every other route is the one the Specter app
itself calls and answers a signed-in session (Authorization: Bearer <access token>); each names
the access class it needs — see Authentication.