If you have an in-house developer or are building a custom application that needs to read or write Intellivizz CRM data programmatically, the public API is the answer. It's a REST API with JSON payloads, OAuth 2.0 authentication, and most resources fully exposed.
Contacts (CRUD, search, custom fields, tags, notes)
Conversations (read threads, send messages)
Calendar (list calendars, create/cancel/reschedule appointments)
Opportunities (CRUD, move stages, list pipelines)
Workflows (trigger, list runs)
Forms and Surveys (read submissions)
Payments (create invoices, list transactions)
Memberships (members, courses, progress)
Locations and Sub-Accounts (agency-level only)
Go to Settings → API & Webhooks
Click "Generate API Key"
Copy the key immediately — you can't view it again, only regenerate
Store it securely in your application's environment variables — never commit it to source control
Use it as a Bearer token in HTTP headers
If you're building an app that other Intellivizz CRM customers will install, use OAuth 2.0 instead of static API keys. This gives each user the ability to authorize and revoke access individually.
Register your app via the Intellivizz CRM marketplace developer portal (or contact [email protected] for early access)
Receive a client_id and client_secret
Implement the standard OAuth 2.0 authorization code flow
Request specific scopes (contacts.read, conversations.write, etc.) — don't request more than you need
| Limit | Value | Action if exceeded |
|---|---|---|
| Requests per minute (per API key) | 100 | Returns HTTP 429 — backoff and retry |
| Requests per day (per API key) | 100,000 | Returns HTTP 429 — contact support to raise |
| Burst (10-second window) | 30 | Spread out heavy operations |
| Bulk endpoints | Special pagination required | See bulk-export docs |
Developer docs: available on request — email [email protected] with subject "API documentation request"
Postman collection: we provide a ready-to-import Postman collection with sample requests for every endpoint
SDK availability: Node.js, Python, and PHP SDKs are community-maintained — official SDK roadmap is in progress
NOTE — HIPAA accounts: API access controls
Medical (HIPAA) plan accounts have additional API restrictions to ensure PHI is never transmitted in plaintext or over non-encrypted connections. Your HIPAA compliance specialist will configure the appropriate scope and signing requirements before issuing API credentials.