Status Codes | Teradata Query Service - RESTful API Status Codes - Teradata Query Service

Teradata® Query Service Installation, Configuration, and Usage Guide for Customers

Teradata Query Service
Release Number
April 2022
English (United States)
Last Update
Product Category
Analytical Ecosystem
The following table lists the status codes in the HTTP response:
Code Definition Description
200 OK Request was successful.
201 Created Request was successful, and the response contains information on the created object.
400 Bad Request Service could not understand the request due to malformed syntax. The client should not repeat the request without modifications.
401 Unauthorized Request requires user authentication.
404 Not Found Resource referenced by the specified URL was not found.
412 Precondition Failed Specified session is currently in use, or there are no available threads to run the request, and the queue timeout has exceeded.
420 Database Error The target Teradata Database returned an error.
429 Too Many Sessions User has reached the session limit.
500 Internal Server Error Service encountered an unexpected condition that prevented it from fulfilling the request.

When the status code is not 200 OK, the response body returns a JSON response containing an error code and error message.

    "message":"Database 'MyDatabase' does not exist.",