Postman & tooling
What exists to save you typing, and what we have deliberately not built.
Postman collection#
Every endpoint on this site, ready to run. It is generated from the router, so it cannot drift into describing something we do not have.
Import it, set the base_url and api_key variables in an environment, and start with a request that carries ?dry_run=1.
MCP endpoint#
https://api.zinevu.com/api/mcp — the same data, read-only, for an assistant. See Connect an assistant.
No SDKs, and why#
There is no official client library. The API is twenty-odd endpoints of plain JSON over HTTPS with a bearer token; a thin SDK per language would be four more things to release on the day we add a field, and the thing it would save you is ten lines of fetch. If a language you work in makes that genuinely painful, tell us — we would rather see the pain than guess at it.
There is no published Zapier or Make app yet. Both can call this API as a plain HTTP action today — bearer header, JSON body, idempotency key on retries — and that is how the integrations running now are built.
Things worth asking for#
- An OpenAPI document, if your toolchain generates clients from one.
- Writes on an endpoint that is read-only today.
- A webhook event for a moment we do not currently publish.
- A higher rate limit for a migration.
None of these are hard; they are unbuilt because nobody has needed them yet. Write to us.