Use the Insyder Public API to read workspace data, analytics, and normalized connection results, and to manage the business data your team owns. The API is RESTful, returns JSON, and is versioned at https://api.insyder.io/v1.
Quickstart
Make your first request, paginate a collection, and update a lead.
Authentication
Create a personal API key and choose its workspaces and scopes.
API reference
Explore every endpoint, parameter, schema, and error response.
| Base URL | https://api.insyder.io/v1 |
| Authentication | X-API-Key: insyder_live_... |
| Format | JSON fields in snake_case; timestamps in UTC ISO 8601 |
| Rate limit | 20 accepted requests per UTC second, per user across all keys |
| Pagination | Cursor-based; 50 records by default and 200 maximum |
| Errors | application/problem+json with stable error codes |
API keys only expose workspaces selected when the key is created, and access is always checked against the owner's current workspace membership. Removing a member or changing their role takes effect immediately.
- Read accounts, leads, content, interactions, historical data, analytics, competitors, and sanitized connection results.
- Update user-managed lead fields: status, email, phone, and notes.
- Create and manage products, create append-only purchases, and prepare expiring exports when the key has the required scope.
- Read normalized iClosed call data and Meta story responses without exposing credentials, raw provider payloads, connection settings, or synchronization controls.
Imported leads, content, interactions, snapshots, scores, runs, and other system-derived facts are read-only. See the API reference for the exact permissions on each operation.
See your iClosed appointments and sales on your Instagram lead profiles. The iClosed integration guide walks you through adding the essential Instagram question to your booking forms, connecting your workspace, and following statuses, products, and sales in Insyder.
See what your Whop business actually received and find each payment on the profile of the lead who made it. The Whop integration guide explains the connection, email matching, the Whop received tile, and matching transactions without a lead by hand.
Insyder has two separate MCP servers. Choose Native MCP to work with your workspace data, or Documentation MCP to learn about the API.
| Native MCP — your data | Documentation MCP — these docs | |
|---|---|---|
| Purpose | Read data and perform the same actions as the public API | Search guides and inspect the API contract |
| Server | https://api.insyder.io/mcp | https://docs.insyder.io/mcp |
| Authentication | OAuth sign-in or API key; approved workspaces, scopes, and role apply | None; public documentation without workspace access |
Connect Claude Desktop, ChatGPT, or another MCP client to your leads, products, purchases, analytics, and exports. The native MCP provides all 51 public API operations.
The native MCP guide covers direct OAuth setup, optional API keys, permissions, every tool, and troubleshooting.
Connect an MCP-compatible assistant to search this documentation and inspect the OpenAPI contract. The published MCP tools are read-only: they do not include an API key, access an Insyder workspace, or execute public API requests.
These buttons connect the documentation server only. It cannot read or change your Insyder data.