The Clink API is currently in development, and available features are limited.
Base Endpoints
The Clink API follows REST principles and requires HTTPS for all requests to ensure data security, integrity, and privacy.
API endpoints for different environments:
Authentication
Clink uses API keys in request headers for security. A dynamic timestamp is also required — in production it must be within 2 minutes of platform time (the sandbox is more lenient). Generate it when you make the call rather than relying on the tolerance window.
Response codes
We use standard HTTP status codes to indicate the outcome of API requests:
2xx codes indicate successful requests
4xx codes indicate client-side errors
5xx codes indicate server-side issues
