The following table contains a list of the most common Error Codes you may get in an API response. Suggested actions and possible solutions are also included.
ERROR CODE | ERROR MESSAGE | ERROR REASON | ACTION / SOLUTION |
-2 | GENERAL ERROR - CALL COULD NOT BE SATISFIED | Your request was timed out for numerous reasons. For example, the retrieved data amount is too large. | Restrict your API call by using the appropriate URL parameters.
Perform the API call in a few minutes. |
10 | SERVICE KEY NOT FOUND | The service key used to perform the API call does not exist in our system. | Make sure you are using the correct API key - you may check here. |
1 | INCORRECT CALL-CHECK PARAMETERS | The most common reason for receiving this error is that the service key is missing. | Make sure that all the required parameters mentioned in the documentation section of each API service are included in the API call. |
1b | MSGTYPE NOT ALLOWED | The msgtype URL parameter requested by the user is not a valid choice. | Try using one of the following values for msgtype: xml/csv/json/jsono |
4 | SERVICE EXPIRED | The API service has expired and should be renewed. | Contact us to renew your subscription. |
3 | SERVICE INACTIVE | The API service is not active either because it has been de-activated by one of the administrators or because it is on a trial period (or saved) and has to be activated. | Contact us to re-activate your API service. |
5 | ABOVE SERVICE CALL LIMIT | All subscription-based MarineTraffic API Services have a call limit depending on their response type. The default values are:
| Contact us if you want to remove or change the call limit. |
12 | SERVICE KEY DOES NOT MATCH SERVICE TYPE | The service key used in order to perform the API call is not corresponding to the API service | Make sure you are using the correct API key - you may check here. |
The following table contains other Error Codes you may get in an API response:
ERROR CODE | ERROR MESSAGE |
-1 | SYSTEM ERROR – PARAMETERS |
1a | INVALID KEY |
7 | FLEET IS EMPTY |
7a | DEFAULT FLEET IS MISSING |
8 | USER NOT FOUND |
9 | MMSI NOT IN ALLOWED LIST |
9a | PORT NOT IN ALLOWED LIST |
9b | STATION NOT IN ALLOWED LIST |
9c | DAYS ABOVE ALLOWED LIMIT |
20 | NOTIFICATION NOT FOUND |
21 | VESSEL NOT FOUND IN FLEET |
100 | IP NOT ALLOWED |
e1 | ERROR WHILE DELETING NOTIFICATION |
e2 | ERROR WHILE ADDING NOTIFICATION |
e3 | ERROR WHILE UPDATING NOTIFICATION |
e4 | ERROR WHILE ADDING VESSEL TO FLEET, EXCEEDED MAXIMUM VESSELS ALLOWED |
e5 | ERROR WHILE DELETING FLEET ITEM |
e6 | ERROR WHILE ADDING FLEET ITEM |
e7 | ERROR WHILE UPDATING FLEET ITEM |
s1 | NOTIFICATION DELETED |
s2 | NOTIFICATION ADDED |
s3 | NOTIFICATION UPDATED |
s5 | FLEET ITEM DELETED |
s6 | FLEET ITEM ADDED |
s7 | FLEET ITEM UPDATED |
e2a | ERROR WHILE ADDING NOTIFICATION, MISSING MMSI AND PORT |
e6a | ERROR WHILE ADDING FLEET ITEM, MISSING MMSI |
1c | BOX POLLING NOT ALLOWED |
1d | TIME-UNLIMITED POLLING NOT ALLOWED |
1e | VERSION NOT ALLOWED |
1f | POLLING RANGE MAXIMUM IS 190 DAYS |
1g | DATE RANGE OUT OF BOUNDS |
1h | START DATE MUST BE GREATER |
2 | VESSEL MMSI OR IMO MISSING |
2a | VESSEL MMSI OR IMO OR PORTID OR UNLOCODE MISSING |
2a1 | VESSEL MMSI OR PORTID MISSING |
2a2 | VESSEL MMSI OR PORTID OR PORTCODE WRONG |
2a3 | VESSEL MMSI NOT FOUND IN DATABASE |
2a4 | VESSEL IMO NOT FOUND IN DATABASE |
2a5 | PORT OR COUNTRY MISSING |
2b | ARRIVAL OR DEPARTURE MISSING |
6 | MMSI NOT IN FLEET |
6a | USER DOES NOT OWN FLEET |
6b | FLEET NOT FOUND |
53 | EMPTY PAYLOAD |
54 | NO SEARCH TERM SUPPLIED |