Developers
Build on AnyImmi. Four surfaces, one firm-scoped auth model.
REST, webhooks, a Chrome extension SDK, and an MCP server for Claude Desktop. Every surface respects CICC rules: no auto-submit to IRCC, DRAFT stamps on AI outputs, row-level security scoped to your firm.
Surfaces
Pick the shape that fits your integration.
REST API
OAuth-scoped, per-firm. Cases, applicants, documents, forms, billing, trust. Paginated, rate-limited, versioned.
Read the docs →Webhooks
Case state transitions, document uploads, payment events, form-signature drift. HMAC-signed. Replay-safe.
Read the docs →Chrome extension
Autofill IRCC portal fields from AnyImmi case data. No auto-submit. Open SDK for firm-specific extensions.
Read the docs →MCP server
Connect Claude Desktop to a firm-scoped AnyImmi workspace. Read-first by default; write actions gated by role.
Read the docs →Quick start
A working API call in under five minutes.
curl https://api.anyimmi.com/v1/cases \ -H "Authorization: Bearer $ANYIMMI_API_KEY" \ -H "Accept: application/json"
Firm admins generate API keys in Settings → Developers. All keys are scoped to a single firm and respect the same row-level security the product uses.
Full reference lives at docs.anyimmi.com.
Schema, auth flows, webhook payloads, MCP tool registry, changelog.