Common issues and solutions when integrating with the Zimark REST API.
Cause: Missing or invalid API key
Solutions:
- Verify
X-AUTH-KEYheader is included in request - Check API key format starts with
ZIM. - Confirm key hasn't been deleted in Backoffice
- Ensure correct environment (staging vs production)
Cause: Invalid request format or missing required fields
Solutions:
- Validate JSON syntax
- Check required fields in API Reference
- Verify date formats match ISO-8601
- Ensure enum values are valid
Cause: Invalid endpoint or resource doesn't exist
Solutions:
- Verify base URL (production vs staging)
- Check endpoint path in API reference
- Confirm resource ID exists
All API requests are logged in the Zimark Backoffice. Use these log to debug integration issues and verify request/response data.
Access logs:
- Navigate to API log
- Filter by date, method, or response status code
- Click a request to view details (headers, body, response)


Use logs to:
- Verify requests reach Zimark
- Debug authentication issues
- Check exact request/response payloads
- Identify webhook delivery problems
Contact Zimark support with:
- Request ID from integration logs
- Error message and status code
- Steps to reproduce