Base URL
All API requests should be made to:Authentication
Include your API key in every request using theAuthorization header:
Available Resources
Leads
Manage and track leads in your workspace
Users
Access workspace members and their information
Identities
Manage visitor identities and their traits
Request Format
AllPOST and PATCH requests should include a Content-Type: application/json header and a JSON body.
Response Format
All responses are returned in JSON format with the following structure:Success Response
Error Response
HTTP Status Codes
OK
Request succeeded
Created
Resource created successfully
Bad Request
Invalid request parameters
Unauthorized
Invalid or missing API key
Forbidden
Access denied to resource
Not Found
Resource not found
Too Many Requests
Rate limit exceeded
Internal Server Error
Server error
Pagination
List endpoints support pagination usinglimit and offset parameters:
- Default: 50 items
- Maximum: 100 items per request
Filtering
Many endpoints support filtering via query parameters:Rate Limiting
All requests are subject to rate limiting. Check the response headers:Timestamps
All timestamps are in ISO 8601 format with UTC timezone:UUIDs
All resource IDs are UUIDs in the format:JSONB Fields
Some fields accept arbitrary JSON objects (properties, traits, etc.):Workspace Scoping
All API requests are automatically scoped to your workspace. You can only access data that belongs to your organization. The workspace ID is included in response headers:SDKs and Libraries
JavaScript/TypeScript
Coming soon
Python
Coming soon
PHP
Coming soon
Ruby
Coming soon
Need Help?
Support
Email our support team
Community
Join our Slack community