The Zinevu API
A REST API over your own data, price writing, and signed webhooks when something changes. Read this page in five minutes, make your first call in five more.
What you can do#
- Read the pipeline. Every lead, offer, customer and line item in your account, filtered and paginated, with an
updated_sincecursor built for incremental syncs. - Put leads in. A form on your own website, a marketplace, a spreadsheet somebody keeps — anything that produces an enquiry can create the lead directly.
- Own your prices elsewhere. Push whole price grids from your ERP, or move a single cell, without opening the portal.
- Run promotions. Start a discount, change it, end it, and spread it over the offers still open — never over one already sent.
- Hear about it. Signed webhooks for the six moments that matter, from a lead arriving to a customer signing.
- Ask in words. An MCP endpoint points Claude, or any assistant that speaks the protocol, at the same data under the same scopes.
At a glance#
| Base URL | https://api.zinevu.com/api/public/v1 |
| Protocol | HTTPS only, JSON in and JSON out, UTF-8 |
| Authentication | Authorization: Bearer zv_live_… — or X-Api-Key |
| Pagination | Cursor, never offset. 25 per page, 100 maximum |
| Timestamps | ISO 8601 with an offset, everywhere, in and out |
| Versioning | The version is in the path — /v1 — and v1 is additive |
| Rate limit | 60 requests a minute per key; writes have their own budget |
| Errors | A stable code at errors.code, prose at meta.message |
One call is worth more than the table. This one needs nothing but a key and tells you what the key can do:
curl https://api.zinevu.com/api/public/v1/me \ -H "Authorization: Bearer zv_live_..."Access#
The API is included from the Pro plan up, along with webhooks. A trial can use it too, on a smaller request budget — enough to build an integration and watch it work. On Starter the API answers 402 with plan_upgrade_required; upgrading switches it on, and any keys already issued keep working.
Keys are created by an account administrator under Settings → Developers. They belong to the account rather than to the person who made them, so removing a colleague never breaks a running integration.
Everything a key reaches is scoped to the account it was minted in. There is no cross-account endpoint, no “list all dealers”, and no way to widen a key after the fact — a scope a key does not carry is a scope it can never gain.