API reference
The complete Zinn Digital® API reference: 1929 endpoints across 56 areas, generated from our OpenAPI specification, with the permission each one needs.
Open →Developer documentation
Everything you need to build on Zinn Digital®
Start from the reference you need, or search every endpoint, command, AI tool and guide at once.
Start with a reference
Pick the part of the platform you are working with.
Webhooks
Send every account event from Zinn® hosting to your own systems as a signed JSON POST. Connect to automation platforms like n8n, Make and Zapier, to CRMs such as HubSpot, Pipedrive and Salesforce, or to anything that accepts a web request.
Open →CLI reference
The complete Zinnector® command reference: 43 commands as `zinnector --help` lists them, each with its flags, a runnable example and what it prints — plus install steps and a two-minute test that proves your setup works.
Open →MCP server
Connect an AI assistant to your hosting over the Model Context Protocol: the exact config for Claude Code, Claude Desktop and Cursor, how two-way sync and deploys work, and all 150 tools, listed from the server itself.
Open →Zinnector®
The free developer CLI: build WordPress locally with nothing but Node, pull a hosted site down and push it back.
Open →Developer platform
Why the platform is API-first, and how sandbox keys, idempotency and permissions work.
Open →Hosting for developers
Git deploys, staging with push-to-live, VS Code in the browser and SSH for every site.
Open →The API, by area
1929 endpoints across 56 areas.
- access · 16 endpoints
- ads · 104 endpoints
- affiliate · 5 endpoints
- agency-board · 89 endpoints
- agency-invoicing · 32 endpoints
- agency-time · 24 endpoints
- ai · 55 endpoints
- api-keys · 4 endpoints
- assistant · 6 endpoints
- audit · 1 endpoints
- billing · 54 endpoints
- board-github · 20 endpoints
- campaigns · 11 endpoints
- Campaigns · 18 endpoints
- catalog · 14 endpoints
- client-reports · 34 endpoints
- commerce · 22 endpoints
- compute · 110 endpoints
- connections · 13 endpoints
- databases · 10 endpoints
- domains · 64 endpoints
- extras · 14 endpoints
- fleet · 4 endpoints
- footprint · 8 endpoints
- hosting · 413 endpoints
- identity · 9 endpoints
- Inbox · 5 endpoints
- links · 48 endpoints
- live-chat · 17 endpoints
- localization · 8 endpoints
- mail · 47 endpoints
- marketplace · 125 endpoints
- mcp · 19 endpoints
- members · 5 endpoints
- notices · 4 endpoints
- notifications · 18 endpoints
- offers · 1 endpoints
- partner · 46 endpoints
- pbs-library · 19 endpoints
- platform-transfers · 9 endpoints
- plugin-support · 7 endpoints
- proposals · 16 endpoints
- public · 76 endpoints
- reseller · 79 endpoints
- security · 4 endpoints
- seo · 3 endpoints
- seo-connect · 81 endpoints
- seo-data · 9 endpoints
- support · 14 endpoints
- surveys · 3 endpoints
- syndication · 14 endpoints
- system · 3 endpoints
- tenancy · 8 endpoints
- visibility · 35 endpoints
- zinn-agents · 14 endpoints
- zinn-campaigns · 38 endpoints
Guides
Step-by-step articles from the knowledge base.
- Working on a site somebody shared with you — A site's owner can hand one site to a developer by email — not their account, not their billing, not their other sites. Both halves: sharing and revoking it from the dashboard, and pulling the site down with zinnector login, clone and dev, database included — plus what each role can and cannot do.
- Troubleshooting Zinnector® — The errors people actually hit with the Zinnector® CLI and the fix for each: spawn EINVAL on Windows, npm's EBADENGINE warning, node-gyp asking for Visual Studio on Node 26, EPERM during install, a runtime that will not boot, and a port in use.
- Zinnector® command reference — Every Zinnector® command exactly as zinnector --help lists it — arguments, flags and defaults, a runnable example and what it prints — generated from the CLI itself so it cannot drift from the version you have installed.
- Deploying with Zinnector®: link, check, push — From a local project to a live site: sign in with an API key, link the project to a hosting slot, read the pre-flight that compares your PHP, disk and WordPress against the slot, and push — plus redeploys, deploy history and build logs when something goes wrong.
- Local development with zinnector dev — How zinnector dev runs a real WordPress on your own machine: the two runtimes (WebAssembly with no Docker, or native PHP in Docker), picking a PHP and WordPress version, what is served from your project, where the 570 MB runtime lives, and what happens on Node 26.
- Getting started with Zinnector®, the developer CLI — Install the free Zinnector® CLI on Node 24 or newer, then prove it works in two minutes: --version, --help, scaffold a site, run a real WordPress locally with no Docker, and open it in your browser — with what success looks like at each step.
- Connecting Claude, Cursor or ChatGPT to your account — Give an AI tool its own scoped token so it can read and manage your hosting — with a spend cap and a sandbox mode.
- Selling Zinn® hosting from your own systems — Drive Zinn® hosting from your own billing panel, WordPress site or scripts: get an API key, make your first call, and the six calls the whole integration is made of.
- Using API keys safely — Scope them, keep them out of your code, and rotate the one you pasted somewhere by accident.
Build against the real platform
Start on a card-free trial, create an API key in the dashboard and make your first call in minutes.