HTTP Headers | Teradata Query Service - HTTP Headers - Teradata Query Service

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

Product
Teradata Query Service
Release Number
4.01.03.01
Published
April 2022
Language
English (United States)
Last Update
2022-06-20
dita:mapPath
xnt1648539781334.ditamap
dita:ditavalPath
ft:empty
dita:id
B035-2700
Product Category
Analytical Ecosystem
The following table lists the mandatory and optional HTTP headers you submit with each request.
Header Value Description Required
Authorization Basic [Base64 encoded "username:password"] Contains credentials used to access the Teradata Database. The Authorization header is constructed as follows:
  1. Username and password are combined into a string ("username:password").
  2. The resulting string is then encoded using the RFC2045-MIME variant of Base64, except not limited to 76 char/line.
  3. The authorization method and a space ("Basic ") is added to the encoded string.
Yes
Accept application/vnd.com.teradata.rest- v1.0+json Instructs the web service that the client wants to use the 1.0 version of the REST API for the Teradata Database. The header supports backward compatibility if the REST API ever changes. Yes
Accept- Encoding gzip Instructs the web service to compress the response in GZIP format. If omitted, the response is returned as plain text. No
Content- Type application/json Instructs the web service that the request contains JSON data. Yes