ioZen Developer Tools: API, Webhooks, and Integrations
ioZen provides a REST API and outbound webhooks for teams that need programmatic access. Build custom integrations, automate workflows, or connect ioZen to your existing systems. Developer tools are part of ioZen’s broader feature set.
What’s available
Section titled “What’s available”| Feature | Plan | What it does |
|---|---|---|
| REST API | Pro+ | Read/write submissions, list bots, manage webhooks |
| Outbound Webhooks | Business | Real-time event notifications to your endpoints |
| API Keys | Pro (3) / Business (10) | Scoped authentication with rate limiting |
REST API
Section titled “REST API”The API lives at https://app.iozen.ai/api/v1/. It follows REST conventions with JSON request/response bodies.
What you can do:
- List and read IntakeBots
- Create and retrieve submissions
- Register and manage webhook endpoints
Every request requires an API key in the Authorization header. Keys are scoped, so you can limit what each integration can access.
Rate limits: Pro gets 100 requests/min, Business gets 500 requests/min. Rate limit headers are included in every response.
For the full endpoint reference, authentication details, and code examples, see the Developer Documentation.
Outbound Webhooks
Section titled “Outbound Webhooks”Webhooks push events to your endpoints in real time. Instead of polling the API, register a URL and ioZen sends HTTP POST requests when things happen.
Events available:
| Event | When it fires |
|---|---|
submission.completed | Someone completes an IntakeBot |
submission.updated | A submission’s data or status changes |
contact.created | A new contact is created |
contact.updated | A contact is updated |
intake-bot.status-changed | A bot’s status changes (ACTIVE → PAUSED, etc.) |
Every webhook payload is signed with HMAC-SHA256, so you can verify it came from ioZen. Failed deliveries are retried automatically with exponential backoff. After 10 consecutive failures, the endpoint is paused.
For signature verification code (Node.js, Python), retry behavior details, and best practices, see the Webhooks Guide.
API Key Management
Section titled “API Key Management”Create and manage keys from Workspace Settings → API Keys. Only Owners and Admins can manage keys.
Scopes available: read:intake-bots, write:intake-bots, read:submissions, read:contacts, read:records, manage:webhooks
Keys follow the iozen_live_ prefix format so they’re easy to detect in git scanners and secret managers. Set expiration dates for temporary access. Revoked keys stop working within 60 seconds.
Next steps
Section titled “Next steps”- Developer Documentation for the full API reference
- Webhooks Guide for event payloads and signature verification
- Integration Guides for ad platform setup (Meta, Google, LinkedIn, TikTok)