Bookshelf Home | Contents | Index | PDF     

Siebel REST API Guide > Overview of Using the Siebel REST API >

About Supported HTTP Header Fields

Certain HTTP header fields define the operating parameters of the REST API transaction with Siebel CRM.

Table 6 contains the HTTP header fields supported by the Siebel REST API.

Table 6. Supported HTTP Header Fields
HTTP Header Field Name
Description
Example

Authorization

The HTTP request header field that indicates the type of authorization. Options include:

  • Basic, if the Authentication type configured in siebsrvr.properties is Basic or SSO
  • Bearer, if the Authentication type configured in siebsrvr.properties is OAuth

Authorization: Basic

Content-Type

The HTTP request and response header field that indicates the content type of the message body. Content-Type decides the format of response for all requests.

The Siebel REST API supports JSON and XML encoding for the request body. The default value is application/JSON.

The Content-Type field is used with POST, PUT, and GET requests. When submitting a POST or PUT 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.

For GET requests, the content type is used to determine the format of response, either XML or JSON.

Content-Type: application/json

      
Siebel REST API Guide Copyright © 2018, Oracle and/or its affiliates. All rights reserved. Legal Notices.