Skip navigation



We have implemented a client for the Eloqua REST API for sending an existing email to an existing contact(EmailTestDeployment).


We are facing the following error when we invoke the API

"Exception occurred while calling method = POST Server returned HTTP response code: 400 for URL:"


The URL and Eloqua Account details are as follows:

base URL :

company : EloquaAutomotiveDemo

account name : Amy.Allen


Do we need to enable Eloqua Engage for this account?

Any help is much appreciated.


Thanks and Regards,



We are attempting to build a client to create a custom object data record using the REST API POST method as documented in this article :


HTTP Status code 500 is received when the method is called with a JSON request containing the custom object data record (field values)


The following are the details of the error encountered : while invoking the method using a Java client: Server returned HTTP response code: 500 for URL:

We verified the that the required custom object exists and its ID is 36 (using REST resource to query Custom object by name)


We tried testing the resource using Chrome Postman Extension and received the following response :

"Internal Server Error

There was an internal server error.

The error has been logged with log identifier 53357258.

Please provide this log identifier to technical support."


We had a couple of queries pertaining to this scenario :

1) Can the REST API be used to create content for an existing email by invoking existing dynamic content rules?What is the REST resource that should be used?

2) How to use the REST API to invoke the email merging to a custom object data record (to be created using REST API as mentioned above)?


Any help would be much appreciated



We found a method in the Eloqua Service SOAP API to create a Data Card(Custom Object Data). However, we would like to know if a REST resource is available


Thanks and Regards,



We are developing a Demo for the Automotive After-Sales,Services and Warranty domain to showcase real-time marketing capability of Eloqua and other products like Oracle Real-Time Decisions (RTD) and Oracle Event Processing (OEP).The flow is implemented as follows :

  1. The Decision process in RTD is invoked when a telematics event occurence is identified in OEP.The Vehicle Identification Number (VIN) is received as part of this event
  2. Offers are defined as Custom Data Objects and Emails in Eloqua
  3. Custom Data Objects(CDO) are used to store offer attributes such as :
    • Name of Dealer presenting the offer
    • Revenue gained when the offer is exercised by the customer
    • Name of the email to be used for presenting the offer (since CDO cannot be linked to an Email and custom fields cannot be added to Email)
  4. RTD retrieves all offers defined in Eloqua using Eloqua REST API to retrieve Custom Data Objects
  5. RTD selects the relevant offer based on :
    • Revenue gained from offer
    • Dealer nearest to the customer's vehicle location (computed using an integration with Oracle Spatial and Graph)
    • Likelihood of Acceptance (Using a prediction model configured in RTD)
  6. In-order to send the email presenting the offer in real-time, Email Deployment('EmailTestDeployment') method of the Eloqua EmailService API is used
  7. However the above method requires the following parameters as input and are obtained as follows :
ParameterObtained Using
Contact ID
  • 'Query' operation of Service SOAP API
  • using Vehicle Identification Number (custom Contact field) value
Email ID
  • 'Query' operation of Service SOAP API
  • using 'E-Mail Name' field value as input

14. The 'Update' operation of the Service SOAP API is used to update the 'Offer' (custom contact field) value with the name of the email sent to customer in the customer's contact


The internal field name(s) to be used to query contact ID/update contact is obtained using 'ListEntityType', 'DescribeEntityType' and 'DescribeEntity' operations

The internal field name(s) to be used to query email ID is obtained using 'ListAssetType', 'DescribeAssetType' and 'DescribeAsset' operations


We had a couple of queries pertaining to this approach :

  • Are there any methods in the REST API to obtain internal field names of Contact
  • Can the above approach of using a combination of the Service SOAP API and the REST API be improved in any manner?


Thanks and Regards,