ERROR CODES - API FOR TIME-SERIES AND TABLES DATA
All REST API requests for time-series and tables must be made using HTTPS. Requests made over HTTP will fail.
You can see the current status and response times for the Nasdaq Data Link REST API for time-series and tables here.
HTTP/Nasdaq Data Link error codes
he Nasdaq Data Link REST API for time-series and tables returns standard HTTP status codes to indicate the success or failure of requests.
A 2XX response indicates that the request was processed successfully.
A 4XX response indicates that there was something wrong with the request.
A 5XX response indicates that the server encountered an error while processing the request.
In addition to HTTP status codes, the Nasdaq Data Link REST API for time-series and tables returns custom error messages for specific error types. These are tabulated below:
|Nasdaq Data Link Error Code||HTTP Status Code||Description|
|QELx01||429||You have exceeded your daily call limit as an anonymous user.|
|QELx02||429||You have exceeded your daily call limit as a registered user.|
|QELx03||429||You have exceeded your daily call limit as a subscriber.|
|QELx04||429||You have exceeded your 10-minute call limit as a registered user.|
|QELx05||429||You have exceeded your 10-minute call limit as a subscriber.|
|QELx06||422||You have requested too many rows of data.|
|QELx07||414||Your request query parameters are too long.|
|QELx08||413||The amount of data you are trying to return is too large. You need to narrow the data returned with filters.|
|QEAx01||400||We could not recognize your API key. Please check your API key and try again. You can find your API key under your account settings.|
|QEAx02||422||Your login credentials are invalid.|
|QEAx03||403||You must have an API key to access this resource.|
|QEPx01||401||You have attempted to view a protected resource in anonymous mode, i.e., without providing an API key. Please register for a free Nasdaq Data Link account and then include your API key with your requests.|
|QEPx02||403||You do not have permission to use this endpoint.|
|QEPx04||403||You do not have permission to view this dataset OR you have exceeded your quota of free trials for this dataset. Please subscribe to this dataset to get more views or downloads.|
|QEPx05||403||You have attempted to view a premium dataset in anonymous mode, i.e., without providing an API key. Please log in or register for a free Nasdaq Data Link account and then include your API key with your requests.|
|QEPx06||403||You do not have access to view part of the data requested (e.g., column).|
|QESx02||422||You are missing a required parameter or its value is empty. Please check your parameters and try again.|
|QESx03||422||You have submitted incorrect parameters for creating/updating this resource. Please check your API call syntax and try again.|
|QESx04||422||You have submitted incorrect query parameters. Please check your API call syntax and try again.|
|QESx05||406||You have requested an unknown format. Please check the format you requested and try again.|
|QESx06||400||You have used an invalid cursor or page ID with your query. Please check your query and try again.|
|QESx07||422||You have used an unsupported operator for your query parameters. Please check and try again.|
|QESx08||422||You have tried to filter a column that is not available for filtering. Please remove and try again.|
|QESx09||400||The syntax of your query parameters is incorrect. Please check the syntax and try again.|
|QECx01||400||Unknown API route. We could not recognize the URL you requested. Please check your URL and try again.|
|QECx02||404||You have submitted an incorrect Table code. Please check your Table codes and try again.|
|QECx03||404||We could not find the resource you requested. Please check your URL and try again.|
|QECx04||404||The referral code is invalid. Please try again.|
|QECx05||422||The URL you requested is incorrect. You may be presented with an alternative URL to use instead.|
|QECx06||404||You cannot make API calls to this dataset. This dataset has been deprecated. Please contact [email protected] for further information.|
|QEMx01||500||Something went wrong. Please try again. If you continue to have problems, please contact us at [email protected]|
|QEXx01||503||The request took too long. Please try again later.|
|QEXx02||502||We are experiencing connectivity issues. Please try again later.|
|QEXx03||500||Something went wrong. Please try again. If you continue to have problems, please contact us at [email protected].|
Updated 8 months ago