HTTP request headers

The sections below outline the request headers used by Oracle Eloqua APIs.


Content-Type specifies the media type that the client is sending to the server. You should always use application/json. If no value is supplied, an error will occur. For example:

PUT https://.../data/contact/123
Content-Type: application/json
<the existing contact>

Important: For PUT and POST verbs, use of the Content-Type header is mandatory.


Accept specifies the media types that the client is willing to accept from the server. If no value is supplied, or if the supplied value doesn't contain application/json, the response will be returned in JSON.

GET https://.../data/contact/123 Accept: application/json

GET https://.../data/contact/123

GET https://.../data/contact/123 Accept: text/html

Note: use of the Accept header is optional.


Allows HTTP clients that don't support the PUT or DELETE verbs to use GET or POST to update and delete entities. If a verb value is supplied in the header, that value will be used in place of the actual request verb. The following examples are functionally identical:

DELETE https://.../data/contact/123

GET https://.../data/contact/123 X-HTTP-Method-Override: DELETE

Note: use of the X-HTTP-Method-Override header is optional.


Allows HTTP clients that don't support or expose HTTP status codes, other than HTTP 200 OK, to indicate that the server should always respond with a specific HTTP status code. If a status code value is supplied in the header, that status code will be used in place of the actual request status code. In the following example, the request will always return HTTP 200 OK, regardless of whether or not the actual status is OK:

GET https://.../data/contact/123 X-HTTP-Status-Code-Override: 200

If a value is supplied for the header, the actual status code will be returned in the X-HTTP-Original-Status-Code response header.

Note: use of theX-HTTP-Status-Code-Override header is optional.