Skip to main content
Send Accept: application/json with every request. Without it, some errors (for example 401 without a key, or 404 for an unknown path) come back as an HTML page instead of JSON.

​
Formats

Errors come in two shapes, depending on where the request stopped. Business and validation errors — 400, 403, 404 and 409 raised by an endpoint — return a list of errors:
Validation errors also name the field: property_path and message_raw. 409 errors carry a machine-readable code. Request-level errors — a missing key, no access, an unknown path or a server error — return a single object:
If something goes wrong on our side, send the traceId to support: it lets us find your request. A wrong API key always returns {"message": "Authentication Failed.", "code": 401}.

​
Status codes

​
Common errors when tracking

These come from Create a conversion, Create a customer and the postbacks. Messages are quoted exactly as the API returns them, so you can match them in your logs. When listing, Invalid date means date_from or date_to isn’t a valid YYYY-MM-DD date.

​
Conflicts

409 responses explain why the object can’t change and include a code: