All API responses from JETNET include two key fields that help identify the status and outcome of each request:
General Troubleshooting Guidelines
- If you see an
ERROR:message, review the exact wording to identify the root cause. - Make sure all required parameters are present and formatted correctly.
- Check if the security token has expired — if so, re-authenticate.
Common Error Responses
- ERROR: INVALID ACCOUNT – The account is not authorized to access the API.
- ERROR: EXPIRED SECURITY TOKEN – Token was valid but has now expired. Re-authentication is needed.
- ERROR: INVALID SECURITY TOKEN – Token is missing, malformed, or invalid.
- ERROR: NO RESULTS FOUND [RECORD NAME] – No match found for the request. Example:
ERROR: NO RESULTS FOUND [AIRCRAFT]
- ERROR: INVALID PARAMETER [PARAMETER NAME] – One or more parameters were invalid. Example:
ERROR: INVALID PARAMETER [AIRCRAFT ID] – [NON-NUMERIC INPUT]
- ERROR: RESULTS EXCEEDED LIMITS [LIMIT] – The number of matching records exceeded the limit.
ERROR: RESULTS EXCEEDED LIMITS [3000]
- ERROR: MISSING REQUIRED PARAMETER [PARAMETER NAME] – A required input was not provided. Examples:
ERROR: MISSING REQUIRED PARAMETER [AIRCRAFT ID]ERROR: MISSING REQUIRED PARAMETER [AT LEAST ONE PARAMETER REQUIRED]
Pro Tip
Most errors are parameter-related or authentication-related. When troubleshooting:
- Double-check your security token and re-auth if needed
- Confirm your parameter names and formats match the Swagger specs