Build on Zinvee
Each Zinvee app has its own API and its own keys. Make a key inside the app, then call it from your own code, n8n, Zapier or Make. Every page here is checked against the app’s code.
The three APIs
Zinvee Work
Tasks, projects, comments, checklists, time and people, read and written as the person who owns the token.
- Personal API tokens, read only or read and write
- Polling on every plan; signed REST hooks on Pro and Business
- An MCP server for AI assistants
Zinvee CRM
Leads, enquiries, follow-ups and your own codes, read out to n8n, a dashboard or a warehouse. Nothing can be changed through it.
- Scoped keys with their own limits
- A change feed that also reports merges and deletes
- Claude, connected read-only
Zinvee Inbox
Contacts, tags and stages, conversations, and sending WhatsApp messages and templates from your own systems.
- Scoped keys
- Signed webhooks as messages arrive and contacts change
- Campaigns and flows, read-only
Side by side
| Work | CRM | Inbox | |
|---|---|---|---|
| Writes | Yes, with a read and write token | No, read-only | Yes, per scope |
| Key | dgt_pat_…, one per person | tcrm_…, one per tool | ik_live_…, one per tool |
| Header | Authorization: Bearer | X-API-Key | Authorization: Bearer |
| Made in | Profile → API tokens | Integrations → Send data out | Settings → API & webhooks |
| Acts as | The token’s owner, with their access | The organization, limited to the scopes ticked | The business, limited to its scopes |
| Rate limit | 120 requests a minute | 120 requests and 2,000 rows a minute, 100,000 rows a day (set per key) | 300 requests a minute |
| Hearing about changes | Polling, or signed REST hooks (Pro and Business) | Polling the change feed | Signed webhooks |
| AI assistants | MCP server | Connect Claude (read-only) | None yet |
AI assistants
Zinvee Work runs an MCP server: an assistant that speaks the Model Context Protocol can search, read and update tasks as you, with a personal API token. A read-only token gives it only the read tools. Set it up.
Zinvee CRM connects to Claude as a custom connector. Claude reads with the permissions of the person who connected it and can never change, call or message anything. It is off until an owner turns it on. How it works.
Good to know
- API keys belong to one app: a Work token doesn’t open CRM or Inbox.
- Every key is shown once when it is made, stored only as a hash, and can be revoked at any time.
- Need something the APIs don’t do yet? Tell us what you are building.