### Error codes and severity levels

| Code | Message | Severity | Details |
|  --- | --- | --- | --- |
| 10000 | Orchestration created successfully | I | Returned by API response on create orchestration. |
| 10001 | No orchestration data found | C | Returned by API response on create orchestration if orchestration data is not passed. Orchestration request is rejected. |
| 10002 | Invalid trade type | C | Returned by API response on create orchestration if trade type code is not recognized. Orchestration request is rejected. |
| 10003 | Invalid port code | C | Returned by API response on create orchestration if port code is not recognized. Orchestration request is rejected. |
| 10004 | Container# {container number} is invalid | C | Returned by API response on create orchestration if container number does not match the expected format. Orchestration request is rejected. |
| 10005 | Missing Bill of Lading | C | Returned by API response on create orchestration if Bill of Lading is not passed. Orchestration request is rejected. If Bill of Lading is passed, but does not match SprintPass Pro’s records, the Guarantee Through Date will be removed from the orchestration to block accidental payments. |
| 10006 | Invalid Guarantee Through Date | C | Returned by API response on create orchestration if Guarantee Through Date does not match the expected format. Orchestration request is rejected. |
| 10007 | Missing Guarantee Through Date | W | Returned by API response and notifications. Payment orchestration will not be initiated. Even if passed correctly, this error will appear in notifications if Bill of Lading does not match. |
| 10008 | Invalid preferences | C | Returned by API response. Orchestration request is rejected. |
| 10009 | Orchestration not found | C | Returned by API on update orchestration if the orchestration does not exist. Request is rejected. |
| 10010 | Orchestration canceled successfully | I | Returned by API response on orchestration cancelation request. All orchestration activities will be stopped. |
| 10011 | Appointment canceled successfully | I | Returned by API response on appointment cancelation request. Orchestration will continue to report status and process payments if applicable. |
| 10012 | {Internal Appointment System message} [{Internal Appointment System code}] | I | Returned by notifications on events received by the internal appointment system. |
| 10013 | {Internal Appointment System message} [{Internal Appointment System code}] | W | Returned by notifications on events received by the internal appointment system, i.e.  no time slots found but orchestration keeps looking, or truck identification required prior to pick up. |
| 10014 | {Internal Appointment System message} [{Internal Appointment System code}] | C | Returned by notifications on events received by the internal appointment system, i.e. no time slots found and threshold exceeded all the options. This error requires action as the appointment attempt has failed and will not be retried. |
| 10015 | Non-matching Bill of Lading | W | Returned by notifications. This message is installed if passed BoL does not match SprintPass Pro’s records. Also, if SprintPass Pro has no record of the BoL. |
| 10016 | Missing container number | C | Returned by API response on orchestration creation request. Request is rejected. |
| 10017 | Missing trade type | C | Returned by API response on orchestration creation request. Request is rejected. |
| 10018 | Missing locations list | C | Returned by API response on orchestration creation request. Request is rejected. |
| 10019 | Missing port code | C | Returned by API response on orchestration creation request. Request is rejected. |
| 10020 | An orchestration is already active for this container | C | Returned by API response on orchestration creation request if the container is already orchestrated by another party. Request is rejected. |
| 10021 | Container not found. | C | Returned by API response on container status request. |
| 10022 | Terminal not supported for payments | W | Returned by notifications after the container is located at terminal where payments are not supported. Orchestration keeps running normally for all supported features. |
| 10023 | Terminal not supported for payments | C | Returned by API response on orchestration update request if Guarantee Through Date is provided. Request is rejected. |
| 10024 | Terminal not supported for appointments | W | Returned by notifications after the container is located at terminal where appointments are not supported. Orchestration keeps running normally for all supported features. |
| 10025 | Terminal not supported for appointments | C | Returned by API response on orchestration update request if any appointment preferences are provided. Request is rejected. |
| 10026 | Unexpected error: reference code#[reference code] | C | Returned by API response and notifications whenever an unexpected error occurs. Manual support required. |
| 10027 | An orchestration for this container is active for another company | C | Returned by API response on orchestration creation request if the container is already orchestrated. Request is rejected. |
| 10028 | Terminal payments not supported. Only third party will be processed | W | Returned by notifications after the container is located at terminal where payments are not supported, except for third party such as PierPass & CleanTruck. Orchestration keeps running normally for all supported features. |
| 10029 | Orchestration update request accepted | I | Returned by API response on successful orchestration update request. |
| 10030 | Empty return not allowed by the terminal | W | Returned by notifications if the terminal does not support empty returns and empty return preferences were passed. Other orchestration features continue to execute normally. |
| 10031 | Updates cannot be passed during a reschedule request | W | Returned by API response on orchestration update request if more fields were passed other than time preferences. Only time preferences will be taken. Other fields will be ignored. Reschedule will be processed normally. |
| 10032 | Appointment not found in given location | C | Returned by API response on orchestration update or cancelation request if no appointment is found for that container. |
| 10033 | Appointment cannot be updated while awaiting response from internal appointment system | C | Returned by API response on orchestration update request if appointment data is passed and the system is waiting to receive acknowledgement of a previous appointment operation. Integrator should retry in this case. |
| 10034 | Container has moved to off-dock yard | I | Returned by notifications if the container has moved to an off-dock location. |
| 10035 | An empty container cannot be the primary in a dual move | C | Dual moves need to be implemented by adding an Empty on top of an existing pick appointment. |
| 10036 | This container has a dual move appointment. | C | The container requested as a dual is already in a dual orchestration. |
| 10037 | Not implemented yet | C | Not implemented yet. |
| 10038 | Invalid secondary container | C | Dual container does not exist or is not gated out yet. For Duals, only gated out empty containers are supported. |
| 10039 | No terminals identified to receive empty line type | C | Even though there are terminals supporting Empty reception, non of them accept this particular container. |
| 10040 | Terminal not identified to receive empty line type | W |  |