Content-Type

The HTTP request and response header field that indicates the content type of the message body. The Oracle CRM On Demand REST API supports only JSON encoding for the request body.

The Content-Type field is used with POST and PATCH requests. When submitting a POST or PATCH request, you typically supply a body with the request. You can indicate the format of the response by setting the HTTP Content-Type header on the request.

Content-Type: application/vnd.oracle.adf.resource+json

Content-Encoding

The HTTP request header field that indicates the encoding for the response message.

Accept-Encoding: gzip, deflate

Content-Language

The HTTP response header that indicates the language the content is in.

Content-Language: da

Accept

The HTTP request header field that indicates the content types that are valid in the response message.

Accept: text/plain

Accept-Language

The HTTP request header that indicates the languages that are valid for the response message. For more information about language formats, see Language Format. For information about supported language codes, see Supported Languages.

Accept-Language: en-US

Location

The HTTP response header that indicates the location of a new resource that has been created.

Location: https://<host>/OnDemand/user/Rest/latest/Accounts/1QA2-21SEFX

LOVLanguageMode

The Oracle CRM On Demand request header field that indicates whether language independent codes (LIC) or language dependent codes (LDC) are returned in the message response. For more information about the LOVLanguageMode input argument, see Special Search Fields.

LOVLanguageMode: LIC

JSESSIONID

The Oracle CRM On Demand response header field that indicates the session ID for login authentication and session management. For more information about login authentication, see Login with Oracle CRM On Demand REST API.

JSESSIONID=sessionidvalue