A preflight can fail for many different reasons. To help clarify an error result, we have assigned integer codes to all of our different types of errors to make them easier for you to catch without having to match text. Note that these error objects are returned as part of the response body when you check the status of an errored preflight through the detail endpoint, and that a preflight can have multiple errors.
| Error Code | Description |
|---|---|
1001 | Missing brand (This error is deprecated in v3 of the Content API, but will occasionally appear in preflights that have been submitted via v1 or v2) |
1002 | Invalid brand |
1003 | Expected only one brand |
1101 | There are no applicable rules for the selected brand, market and/or channel. |
2001 | Missing market (This error is deprecated in v3 of the Content API, but will occasionally appear in preflights that have been submitted via v1 or v2) |
2002 | Invalid market |
3001 | Missing channel (This error is deprecated in v3 of the Content API, but will occasionally appear in preflights that have been submitted via v1 or v2) |
3002 | Invalid channel |
3003 | Expected only one channel |
4001 | Missing publisher (This is used when the selected channel requires a publisher), Missing placement (This is used when the selected publisher requires a placement) |
4002 | Invalid publisher, Invalid placements |
4004 | Placements are required for selected publisher |
4101 | There are no applicable rules for the selected placements, campaign objective or publisher |
5002 | Invalid campaign objective |
6002 | Invalid ad format |
7002 | Invalid content type |
8002 | Invalid creative type |
8005 | Could not open source URL |
8101 | There are no applicable rules for the selected creatives |
8102 | Could not download creatives |
8999 | Error processing creatives |
9999 | Creative is broken and unable to be reviewed |
These error codes are different from the HTTP error responses generated by the API itself, which are generally caused by parameter errors or problems with authentication. If you have any questions about parameter errors, please refer to the documentation for the endpoint.