What You Can Do
With the Clix API, you can:- Manage Users - Create, update, and delete project users; store and update custom user properties for segmentation and personalization
- Send Messages - Deliver push notifications directly to user devices with custom content
- Trigger Campaigns - Trigger pre-configured campaigns to specific users or broadcast to your entire user base
Base URL
Authentication
Every Clix API request requires authentication through two custom headers that identify your project and authorize the request:API Key Types and Use Cases
Clix distinguishes between two API key types to provide flexibility and security:Key Selection Guide
- Public Key: Use for direct SDK integrations where your application frontend communicates with Clix
- Secret Key: Use for sensitive operations including user management, message sending, and campaign triggering
Example Request
Protecting Your API Keys
- Store keys in environment variables or dedicated secrets management platforms
- Implement key rotation policies in your organization
- Apply the principle of least privilege—use Public keys in client applications, Secret keys only in trusted backends
- Regularly audit API key usage and revoke unused keys
- Enable alerts if unusual API activity is detected
Rate Limits
Rate limits are applied to ensure fair usage and maintain service stability. If you exceed your rate limit, the API will return a429 Too Many Requests response.
For detailed information about rate limiting policies and best practices, see Rate Limits.
Content Type
The Clix API exclusively uses JSON for request and response bodies.Response Codes and Error Handling
Clix API responses follow standard HTTP conventions. The status code indicates the outcome of your request:Success Codes
Client Error Codes
Server Error Codes
Error Response Format
When a request fails, the response body contains an error message:Implementing Reliable Retries
For production integrations, implement exponential backoff to handle transient failures gracefully:OpenAPI Specification
The complete OpenAPI specification for the Clix API is available:OpenAPI Spec
View the complete OpenAPI specification
API Endpoints
Users
Store and manage your project’s user profiles. Users can have custom properties used for segmentation, personalization, and targeting.- Create User - Register a new project user
- Update User - Modify user properties and attributes
- Delete User - Permanently remove a user from your project
Campaigns
Campaigns are pre-configured message templates set up in your dashboard. Use the API to trigger campaigns to reach your users.- Trigger Campaign - Execute a campaign, targeting specific users or broadcast to all users matching campaign filters
Messages
Send ad-hoc push notifications outside of campaigns. Useful for transactional or time-sensitive messages.- Send Messages - Deliver push notifications directly to specified devices
SDK Integration
For easier integration, consider using our official SDKs:Request Timeout
API requests have a maximum execution time of 100 seconds. If your request doesn’t complete within this window, it will be terminated with a timeout error. Ensure your integration handles timeouts gracefully.Integration Guidelines
Build robust integrations with these recommendations:- Always use HTTPS - Connections must be encrypted with TLS 1.2 or higher
- Implement exponential backoff - Automatically retry on 5xx errors with increasing delays (1s, 2s, 4s…)
- Respect rate limits - Monitor response status and throttle requests to stay within limits
- Log responses - Track API responses for debugging and monitoring
- Validate inputs - Check that project user IDs and other identifiers match expected formats
- Choose keys wisely - Use Public keys for SDKs, Secret keys only for backend services
Support
Need help? Contact our support team:- Email: [email protected]
- Documentation: https://docs.clix.so