Skip to main content

Error Code

  • This section provides a mapping between v2 and v3 API error codes and their corresponding reasons.
  • How error reasons are presented:
    • In v2 API, the reason field contains an Error Code representing the issue.
    • In v3 API, the reason field contains a Description instead of a numeric code.
Error CodeDescriptionMessage
1RESOURCE_DUPLICATEDDuplicate
2SHIPMENT_INTERNALError from internal shipment API
3RESOURCE_NOT_FOUNDResource not found
4CREDIT_NOT_ENOUGHInsufficient credits
5COLLECT_NOT_ACCEPTInvalid LineCd or B/L; unable to retrieve
6VERIFY_FAILValidation failed
7CONTRACT_NOT_FOUNDContract not found
8UNAUTHORIZEDAuthentication failed
9RESOURCE_FULLExceeded resource limit
10TRADLINX_CREDIT_INTERNALError checking Tradlinx credit balance
11INVALID_REQUESTInvalid user request
12CONTRACT_EXPIREDContract has expired
13DISAGREE_SHIPGO_USER_TERMUser terms not agreed to
14UNSUPPORTED_FEATUREFeature not supported in current plan
1000UNKNOWNUndefined error

Example Response

V2 API Example

{
"api_version": "v2",
"transaction_time": "2024-11-14T04:40:30.790634",
"content": {
"success": [],
"fail": [
{
"data": {
"line_cd": "HMM",
"bl_no": "BL123456789"
},
"reason": "5"
}
],
"total_count": 1,
"success_count": 0,
"fail_count": 1
}
}

V3 API Example

{
"api_version": "v3",
"transaction_time": "2024-11-14T04:40:30.790634",
"content": {
"success": [],
"fail": [
{
"data": {
"line_cd": "HMM",
"bl_no": "BL123456789"
},
"reason": "COLLECT_NOT_ACCEPT"
}
],
"total_count": 1,
"success_count": 0,
"fail_count": 1
}
}

Summary

  • v2 API: Use Error Code code for reason (e.g. "5").
  • v3 API: Use Description for the reason (e.g. "COLLECT_NOT_ACCEPT").
  • The two APIs provide the same error information in different ways.