What it does
Give an outside tool its own key instead of a staff login. Keys are read-only and scoped; webhooks push events out as they happen. The base URL is https://api.zentive.io/public-api/v1.
Create an API key
- 1
Settings → Public Integrations → Create Integration API Key
Name it for the tool (Zapier Read Key) and tick only the scopes it needs: Customers, Jobs, Invoices, Quotes, Leads (all read).
- 2
Copy the key once
It is shown once. Send it as X-Zentive-Api-Key: <key> or Authorization: Bearer <key>.
- 3
Endpoints
GET /customers, /jobs, /invoices, /quotes, /leads with limit, page, status, source, and q (search) parameters as listed on the page.
Create a webhook
- 1
Create Webhook Subscription
Name, Target URL (https), and event types: Lead Created, Quote Created, Quote Status Changed.
- 2
Verify deliveries
Each request carries X-Zentive-Signature-256 (HMAC SHA-256 of the body with your signing secret), X-Zentive-Event-Type, and X-Zentive-Webhook-Id. Recent Webhook Delivery Logs shows every attempt with status code and response.
Did this solve your problem?
Contact Zentive support
Tell us what happened and what you have already tried. We will include this article so you do not have to start over.