Help
Heyzack CRM REST API overview
Learn the base URL, versioning scheme, request and response format, authentication header, and HTTP status codes for the Heyzack CRM API.
The Heyzack CRM REST API lets you integrate portal functionality—messaging, connections, and more—directly into your own applications. Every endpoint uses JSON over HTTPS, requires a Bearer token for authentication, and wraps successful responses in a consistent data envelope.
Base URL
All API requests are made to:
https://<your-portal-domain>/api/v1Replace <your-portal-domain> with the domain of your Heyzack CRM instance.
Versioning
The current API version is v1. The version is embedded in every URL path (/api/v1/...). When a new major version is released, the older version remains available at its existing path until a deprecation period ends.
Request format
For POST endpoints, send a JSON body and include the Content-Type header:
Content-Type: application/jsonGET endpoints accept parameters as URL query strings instead.
Authentication
Every request requires a Bearer token in the Authorization header:
Authorization: Bearer <your-token>See Authentication for details on obtaining and using tokens.
Response format
Successful responses return HTTP 200 and wrap the result in a data key:
{
"data": { ... }
}Error responses
When a request fails, the API returns a JSON object with an error key describing what went wrong:
{
"error": "Error message here"
}HTTP status codes
| Code | Meaning |
|---|---|
| 200 | Success |
| 400 | Bad request — missing or invalid parameters |
| 401 | Unauthorized — missing or invalid token |
| 403 | Forbidden — valid token but insufficient permissions |
| 404 | Resource not found |
| 500 | Internal server error |