Changelog

View changes for Eloqua's APIs including:

New features
Significant recent changes
Platform notices

Included in these changelogs are the Application API, Bulk API, and AppCloud Developer Framework.

To learn more about recent and upcoming Oracle Eloqua release rollouts, including rollout dates, user-facing features, and product notices, visit the Oracle Eloqua Release Center.

Release 24B

Bulk API

When attempting to delete data using the data endpoints when there is an associated sync in progress, we will now return a “409 There was a conflict.” validation response. For more information, see the product notice.
Resolved an issue where if both IsBounced and IsSubscribed are set to 1 on Bulk API contact import only IsSubscribed would successfully be set to 1.

Application API

CampaignId added to fieldValues for SMS activities for the Application API 2.0 Retrieve a list of activities endpoint. For more information, see the product notice.

Reporting API

The reporting API is now Generally Available. Learn more.

Platform notices

With the arrival of Eloqua release 24C (August 2024), there will be a limit of 500 files per Bulk API import / sync action sync. For more information, see the product notice.

Documentation enhancements of note

New best practice for exporting contacts in a Segment / Shared Filter added to Bulk API Best Practices.
Details on the limit for searching custom object data added to the Using the search URL parameter tutorial.
Details on the authorization flow limit added to Authenticate using OAuth 2.0.
Examples using IsBounced and IsSubscribed in a Bulk API export definition filter added to Filtering.

Release 24A

Bulk API

The Bulk API default dataRetentionDuration for exports will now be 6 hours. For more information, see the product notice.
New bounceback sync action available with Bulk API email address import definition which enables changing the bounceback status of an email address without having to create a contact. An email address can be set to unsubscribed or bounced but not both. For more information, see Sync actions.
All CSV exports, including the Bulk API, will escape formulas by prepending each cell field with a formula with a single quote. For more information, see the product notice.

Application API

GET requests using the Application API will be controlled by the new form action permissions for the following endpoints:

2.0 Endpoints

Retrieve processed form data for a single form: GET /API/REST/2.0/data/form/{id}
Retrieve all spam form submit jobs for a single form: GET /API/REST/2.0/data/form/{formid}/formSpamData
Retrieve all form submit jobs for a single form: GET /API/REST/2.0/data/form/{formid}/formData
Retrieve a single form submit job: GET /API/REST/2.0/data/form/{formid}/formData/{formSubmitJobId}
Retrieve batch form submission details by batchId: GET /API/REST/2.0/data/form/{formid}/batch/formData/{batchid}
Retrieve batch form submission details by batchCorrelationId: GET /API/REST/2.0/data/form/{formid}/batchCorrelation/formData/{batchcorrelationid}

1.0 Endpoints

Retrieve a single form submit job: GET /API/REST/1.0/data/form/{formId}/formData/{formSubmitJobId}
Retrieve all form submit jobs for a single form: GET /API/REST/1.0/data/form/{formId}/formData
Retrieve processed form data for a single form: GET /API/REST/1.0/data/form/{id}

Release 23D

Application API

Application API Campaign endpoints will now include campaignClassification at minimal depth
Application API canvas create and update endpoints will now return a more detailed validation error when evaluateNoAfter is not valid
Application API Retrieve an email endpoint will now return the destination links for Email Components within the htmlContent properties html and htmlBody when the noMergeContent query parameter is set to false
Application API Form endpoints to include new properties when form spam protection is enabled and isFormSpamProtection is set to “true”:
- isAutoClickProtectionEnabled
- isCustomHoneypotHtmlNameEnabled
- formSpamTimeInterval
More information is available within our Product Notices in the Oracle Marketing Developer Tools area within the Cloud Customer Connect community.

New/Updated Application API endpoints for SMS are now available:

SMS Asset Management
- POST /API/REST/2.0/assets/sms
- PUT /API/REST/2.0/assets/sms/{id}
- GET /API/REST/2.0/assets/sms/{id}
- GET /API/REST/2.0/assets/sms
- DELETE /API/REST/2.0/assets/sms/{id}
SMS Folder Management
- POST /API/REST/2.0/assets/sms/folder
- GET /API/REST/2.0/assets/sms/folder/{id}
- PUT /API/REST/2.0/assets/sms/folder/{id}
- DELETE /API/REST/2.0/assets/sms/folder/{id}
- PATCH /API/REST/2.0/assets/sms/folder/{id}/contents
- GET /API/REST/2.0/assets/sms/folder/root
- GET /API/REST/2.0/assets/sms/folder/{id}/contents
- GET /API/REST/2.0/assets/sms/folder/root/contents
- GET /API/REST/2.0/assets/sms/folder/root/folders
- GET /API/REST/2.0/assets/sms/folder/{id}/folders
- GET /API/REST/2.0/assets/sms/folders
SMS Setup
- View Codes
  - GET /API/REST/2.0/assets/sms/senderCodes
- Manage Keywords
  - POST /API/REST/2.0/assets/sms/keyword
  - GET /API/REST/2.0/assets/sms/keywords
  - GET /API/REST/2.0/assets/sms/keyword/{id}
  - DELETE /API/REST/2.0/assets/sms/keyword/{keywordId}
- Manage Invalid Keyword Messages
  - POST /API/REST/2.0/assets/sms/invalidResponseMessage
  - GET /API/REST/2.0/assets/sms/invalidResponseMessages
  - GET /API/REST/2.0/assets/sms/invalidResponseMessage/{id}
  - PUT /API/REST/2.0/assets/sms/invalidResponseMessage/{id}
  - DELETE /API/REST/2.0/assets/sms/invalidResponseMessage/{id}
A new parameter, isSmsSubscribed, is added to the existing Contact API retrieve contact information 2.0 endpoint. This gives a contact’s global subscription status for SMS.
New Activities API 2.0 endpoints
- GET /api/rest/2.0/data/activities/contact/{id}/{type}, retrieve a list of activities of a contact including SMS activities. Learn more.
New Phone Number consent Management API 2.0 endpoints
- POST /API/REST/2.0/data/sms/subscription (X-HTTP-Method-Override=SEARCH), a maximum of 10 phone numbers can be passed in a single request
- PUT /API/REST/2.0/data/sms/subscription
Campaign 2.0 endpoints now support SMS steps
Contact segment 2.0 endpoints now support SMS based filters
Security group 2.0 endpoints now support SMS related settings

Bulk API

New/Updated Bulk API endpoints for SMS are now available:

We’ve introduced new phone Number consent import endpoints. You can import phone numbers & it’s consent (Opt-In/Opt-Out) using it, the fields are: {{PhoneNumber.Field(PhoneNumber)}}, {{PhoneNumber.Field(Preference)}} . {{PhoneNumber.Field(Preference)}} must be set to Opt-Out or Opt-In, if there are duplicates, e.g. the Phone Number is repeated, the duplicates will be rejected. Phone numbers must be valid, otherwise they will be rejected.
Below are the new endpoints:
- Create a phone number import definition (POST /api/bulk/2.0/phoneNumbers/imports)
- Update existing phone number import definition (PUT /api/bulk/2.0/phoneNumbers/imports/{id})
- Retrieve a list of phone number import definitions (GET /api/bulk/2.0/phoneNumbers/imports)
- Retrieve a single phone number import definition (GET /api/bulk/2.0/phoneNumbers/imports/{id})
- Delete phone number import definition (DELETE /api/bulk/2.0/phoneNumbers/imports/{id})
- Upload data to phone number definition (POST /api/bulk/2.0/phoneNumbers/imports/{id}/data)
- Delete data from phone number definition (DELTE /api/bulk/2.0/phoneNumbers/imports/{id}/data)
Phone number consent & SMS Global Subscription fields are now included on Contact export endpoints.
- {{Contact.SMS.IsOptedIn}}
- {{Contact.SMS.MobilePhone.IsOptedIn}}
- {{Contact.SMS.BusPhone.IsOptedIn}}

The possible field values are true or false. You can also use the fields for filtering.

Release 23C

Bulk API

External Activities are available to export via Bulk API - one of our top Dream It idea requests!
- New Activity Type: ExternalActivity
- ExternalActivity Fields:
  - Activity.Id
  - Activity.Type
  - Activity.CreatedAt
  - Activity.ExternalAssetType
  - Activity.ExternalAssetName
  - Activity.ExternalActivityType
  - Activity.Campaign.Id
  - Activity.Contact.Id
  - Activity.ExternalId
- Use the following request to retrieve all available fields for External Activities:
  - GET /api/Bulk/2.0/activities/fields?activityType=ExternalActivity
  Learn more about the export definition.
Bulk API definition deletion when App uninstalled. For more information, see the product notice.

Application API

New Lookup Table Application API endpoints:
- Retrieve
  - GET /api/rest/2.0/assets/lookupTables
  - GET /api/rest/2.0/assets/lookupTable/{id}
  - GET /api/rest/2.0/data/lookupTable/{parentId}/lookupTableEntries
- Update
  - PUT /api/rest/2.0/assets/lookupTable/{parentId}/LookupTableEntry/{key}
- Delete
  - DELETE /api/rest/2.0/assets/lookupTable/{parentId}/LookupTableEntry/{key}
A new property, isExitHistoryDisabled, will be added to the Application API Campaign and Program endpoints. For more information, see the product notice.

Release 23B

A list of developer-facing new features, significant recent changes, and platform notices for Oracle Eloqua release 23B.

Application API

API endpoints now available to manage asset folders:

Campaign folders
- POST /API/REST/2.0/assets/campaign/folder
- GET /API/REST/2.0/assets/campaign/folders
- PUT /API/REST/2.0/assets/campaign/folder/{id}
- GET /API/REST/2.0/assets/campaign/folder/{id}
- DELETE /API/REST/2.0/assets/campaign/folder/{id}
- PATCH /API/REST/2.0/assets/campaign/folder/{id}/contents
- GET /API/REST/2.0/assets/campaign/folder/{id}/contents
- GET /API/REST/2.0/assets/campaign/folder/{id}/folders
- GET /API/REST/2.0/assets/campaign/folder/root/folders
- GET /API/REST/2.0/assets/campaign/folder/root/contents
- GET /API/REST/2.0/assets/campaign/folder/root

Email folders
- POST /API/REST/2.0/assets/email/folder
- GET /API/REST/2.0/assets/email/folders
- PUT /API/REST/2.0/assets/email/folder/{id}
- GET /API/REST/2.0/assets/email/folder/{id}
- DELETE /API/REST/2.0/assets/email/folder/{id}
- PATCH /API/REST/2.0/assets/email/folder/{id}/contents
- GET /API/REST/2.0/assets/email/folder/{id}/contents
- GET /API/REST/2.0/assets/email/folder/{id}/folders
- GET /API/REST/2.0/assets/email/folder/root/folders
- GET /API/REST/2.0/assets/email/folder/root/contents
- GET /API/REST/2.0/assets/email/folder/root

Form folders
- POST /API/REST/2.0/assets/form/folder
- GET /API/REST/2.0/assets/form/folders
- PUT /API/REST/2.0/assets/form/folder/{id}
- GET /API/REST/2.0/assets/form/folder/{id}
- DELETE /API/REST/2.0/assets/form/folder/{id}
- PATCH /API/REST/2.0/assets/form/folder/{id}/contents
- GET /API/REST/2.0/assets/form/folder/{id}/contents
- GET /API/REST/2.0/assets/form/folder/{id}/folders
- GET /API/REST/2.0/assets/form/folder/root/folders
- GET /API/REST/2.0/assets/form/folder/root/contents
- GET /API/REST/2.0/assets/form/folder/root

Hyperlink folders
- POST /API/REST/2.0/assets/hyperlink/folder
- GET /API/REST/2.0/assets/hyperlink/folders
- PUT /API/REST/2.0/assets/hyperlink/folder/{id}
- GET /API/REST/2.0/assets/hyperlink/folder/{id}
- DELETE /API/REST/2.0/assets/hyperlink/folder/{id}
- PATCH /API/REST/2.0/assets/hyperlink/folder/{id}/contents
- GET /API/REST/2.0/assets/hyperlink/folder/{id}/contents
- GET /API/REST/2.0/assets/hyperlink/folder/{id}/folders
- GET /API/REST/2.0/assets/hyperlink/folder/root/folders
- GET /API/REST/2.0/assets/hyperlink/folder/root/contents
- GET /API/REST/2.0/assets/hyperlink/folder/root

Image folders
- POST /API/REST/2.0/assets/image/folder
- GET /API/REST/2.0/assets/image/folders
- PUT /API/REST/2.0/assets/image/folder/{id}
- GET /API/REST/2.0/assets/image/folder/{id}
- DELETE /API/REST/2.0/assets/image/folder/{id}
- PATCH /API/REST/2.0/assets/image/folder/{id}/contents
- GET /API/REST/2.0/assets/image/folder/{id}/contents
- GET /API/REST/2.0/assets/image/folder/{id}/folders
- GET /API/REST/2.0/assets/image/folder/root/folders
- GET /API/REST/2.0/assets/image/folder/root/contents
- GET /API/REST/2.0/assets/image/folder/root

Release 23A

A list of developer-facing new features, significant recent changes, and platform notices for Oracle Eloqua release 23A.

Application API

API endpoints now available to manage User Security Groups:
- GET /system/security/group/{id}/users
- PATCH /system/security/group/{id}/users
- DELETE /system/security/group/{id}
- PUT /system/security/group/{id}
- GET /system/security/group/{id}
- POST /system/security/group
- GET /system/security/groups
Retrieve visitor data change: When retrieving visitor data using the Retrieve visitor data Application API 2.0 endpoint visitorId will now be a BigInt. Previously, visitorId was an Integer.

Eloqua Form Application API changes: When a form is created, updated, or retrieved using the Application API 2.0 endpoints, the response body will return all mapped and unmapped fields present on the form for the processing steps to update Contacts, Accounts, and Custom Objects with form data. Previously, only fields included within the processing steps when the form was created or updated were returned by the response body. For more information, see the product notice.

The following Application API 2.0 processing step endpoints are impacted:

Create a form POST /api/rest/2.0/assets/form
Retrieve a form GET /api/rest/2.0/assets/form/{id}
Update a form PUT /api/rest/2.0/assets/form/{id}
Partially update a form PATCH /api/rest/2.0/assets/form/{id}

The following processing step types are impacted:

"type": "FormStepCreateUpdateContactFromFormField"
"type": "FormStepCreateUpdateAccountFromFormField"
"type": "FormStepCreateUpdateCustomObjectFromFormField"

See an example

Pre 23A

Request

GET /api/rest/2.0/assets/form/12345

Response

{
"type": "Form",
    	"currentStatus": "Draft",
    	"id": "12345",...
    	"elements": [
        	{
            	"type": "FormField",
            	"id": "2584",
            	"name": "Email",
            	...
        	},
       	 {
            	"type": "FormField",
            	"id": "2583",
            	"name": "City",
			...
        	},
        	{
            	"type": "FormField",
            	"id": "2592",
            	"name": "Favorite Colour",
            	...
        	},
        	{
            	"type": "FormField",
            	"id": "2587",
            	"name": "Submit",
            	...
       	 }
    	],...
    	"processingSteps": [
       	{
            	"type": "FormStepCreateUpdateContactFromFormField",
            	"id": "1826",
            	"name": "Create / Update Contact, Prospect or Company",
            	"execute": "always",
            	"keyFieldId": "100001",
            	"mappings": [
                	{
                    	"type": "FormFieldUpdateMapping",
                    	"sourceFormFieldId": "2583",
                    	"targetEntityFieldId": "100009",
                    	"updateType": "useFieldRule"
                	},
                	{
                    	"type": "FormFieldUpdateMapping",
                    	"sourceFormFieldId": "2584",
                    	"targetEntityFieldId": "100001"
                	}
            	]
        	}
   	],…
}

Post 23A

Request

GET /api/rest/2.0/assets/form/12345

Response

{
"type": "Form",
    	"currentStatus": "Draft",
    	"id": "12345",...
    	"elements": [
        	{
            	"type": "FormField",
            	"id": "2584",
            	"name": "Email",
            	...
        	},
       	 {
            	"type": "FormField",
            	"id": "2583",
            	"name": "City",
			...
        	},
        	{
            	"type": "FormField",
            	"id": "2592",
            	"name": "Favorite Colour",
            	...
        	},
        	{
            	"type": "FormField",
            	"id": "2587",
            	"name": "Submit",
            	...
       	 }
    	],...
    	"processingSteps": [
       	{
            	"type": "FormStepCreateUpdateContactFromFormField",
            	"id": "1826",
            	"name": "Create / Update Contact, Prospect or Company",
            	"execute": "always",
            	"keyFieldId": "100001",
            	"mappings": [
                	{
                    	"type": "FormFieldUpdateMapping",
                    	"sourceFormFieldId": "2583",
                    	"targetEntityFieldId": "100009",
                    	"updateType": "useFieldRule"
                	},
			{
				"type": "FormFieldUpdateMapping",
				"sourceFormFieldId": "2592",	
			},
                	{
                    	"type": "FormFieldUpdateMapping",
                    	"sourceFormFieldId": "2584",
                    	"targetEntityFieldId": "100001"
                	}
            	]
        	}
   	],…
}

409 Concurrent Form Update Error: Multiple concurrent updates for forms using the Oracle Eloqua UI or the Application APIs 1.0 and 2.0 endpoints will now be prevented. A 409 Conflict response will be returned via API, and in the UI a warning box will appear. For more information, see the product notice.
The following endpoints now return a 409 Conflict response:
- Update a form version 1.0 PUT /api/REST/1.0/assets/form/{id}
- Update a form version 2.0 PUT /api/rest/2.0/assets/form/{id}
- Partially update a form PATCH /api/rest/2.0/assets/form/{id}
See an example
Example 409 conflict response:
Request (more than one at the same time to this endpoint):
PUT /api/rest/2.0/assets/form/12345
Response
```
Header: 409 CONFLICT
Body:
[{"type":"ConcurrentUpdateError","details":"Your save was not
completed due to a recent modification of this form by another
user."}]
```

Release 22D

A list of developer-facing new features, significant recent changes, and platform notices for Oracle Eloqua release 22D.

New features

Bulk API

Bulk API contact app exports can now include source Campaign ID and fields. When a contact is moved from a Campaign Canvas to a Program Canvas the source Campaign Canvas will now be tracked. The Source Campaign ID and fields can then be included in a Bulk API Contact app export within the Program Canvas. Include the Campaign ID using the following statement: {{Contact.SourceCampaign.Id}}. Add the source Campaign fields using this syntax: {{Contact.SourceCampaign.Field(<FieldName>)}}. If a SourceCampaign field is included in an export definition that is not for a Program Canvas app, the export definition creation will fail.
All Special Fields (e.g. Id) are now included in Fields endpoints.
- {{Contact.Email.IsSubscribed}}
- {{Contact.Email.IsBounced}}
- {{Contact.Email.Format}}
- {{Contact.Id}}
- {{Account.Id}}
- {{CustomObject[<customObjectId>].Id}}
- {{Event[<eventId>].Id}}

Platform notices

With the arrival of Eloqua 22D release (November 2022), the EloquaService SOAP API will be deleted. For more information, see the product notice.

Release 22C

A list of developer-facing new features, significant recent changes, and platform notices for Oracle Eloqua release 22C.

New features

Application API

We have added a new property isUpdatingCrmID to the Update a campaign endpoint. This property indicates if crmId is being updated. For more information, see the product notice.

Bulk API

We have added new opportunity fields Owner and PrimaryCampaignID for Bulk API import. You can retrieve these new opportunity fields using the API endpoint: GET/API/Bulk/2.0/opportunities/fields.

See the API reference for more information.

See an example

HTTP request

POST /opportunities/imports
							Content-Type: application/json

Request body

{
								"name": "Opportunity Import",
								"fields": {
								"OpportunityID": "{{Opportunity.Id}}",
								"OpportunityName": "{{Opportunity.Field(Name)}}",
								"AccountName": "{{Opportunity.Field(AccountName)}}",
								"CreatedDate": "{{Opportunity.CreatedAt}}",
								"Amount": "{{Opportunity.Field(Amount)}}",
								"CloseDate": "{{Opportunity.Field(CloseDate)}}",
								"Currency": "{{Opportunity.Field(Currency)}}",
								"ForecastToCloseDate": "{{Opportunity.Field(ForecastToCloseDate)}}",
								"Stage": "{{Opportunity.Field(Stage)}}",
								"Territory": "{{Opportunity.Field(Territory)}}",
								"Owner": "{{Opportunity.Field(Owner)}}",
								"PrimaryCampaignId": "{{Opportunity.Field(PrimaryCampaignId)}}"
								},
								"identifierFieldName": "OpportunityID",
								"isIdentifierFieldCaseSensitive": false
							}

Response

{
								"isIdentifierFieldCaseSensitive": false,
								"name": "Opportunity Import",
								"fields": {
								"OpportunityID": "{{Opportunity.Id}}",
								"OpportunityName": "{{Opportunity.Field(Name)}}",
								"AccountName": "{{Opportunity.Field(AccountName)}}",
								"CreatedDate": "{{Opportunity.CreatedAt}}",
								"Amount": "{{Opportunity.Field(Amount)}}",
								"CloseDate": "{{Opportunity.Field(CloseDate)}}",
								"Currency": "{{Opportunity.Field(Currency)}}",
								"ForecastToCloseDate": "{{Opportunity.Field(ForecastToCloseDate)}}",
								"Stage": "{{Opportunity.Field(Stage)}}",
								"Territory": "{{Opportunity.Field(Territory)}}",
								"Owner": "{{Opportunity.Field(Owner)}}",
								"PrimaryCampaignId": "{{Opportunity.Field(PrimaryCampaignId)}}"
								},
								"identifierFieldName": "OpportunityID",
								"isSyncTriggeredOnImport": false,
								"dataRetentionDuration": "P7D",
								"uri": "/opportunities/imports/6769",
								"createdBy": "API.User",
								"createdAt": "2022-06-13T14:02:29.6270000Z",
								"updatedBy": "API.User",
								"updatedAt": "2022-06-13T14:02:29.6270000Z"
							}

Recent changes

Application API

We have added a new search parameter isCertificateProvisioned to the Retrieve a list of microsites endpoint. Set isCertificateProvisioned to “true” to filter on microsites that have a certificate provisioned for at least one of your domains. If isCertificateProvisioned is not included in request all microsites will be returned.

Platform notices

With the arrival of Eloqua 22D release (November 2022), the EloquaService SOAP API will be deleted. For more information, see the product notice.

Release 22B

A list of developer-facing new features, significant recent changes, and platform notices for Oracle Eloqua release 22B.

New features

Application API

We've added a new query parameter that enables you to retrieve a list of Microsites provisioned using the Automated Certificate Management system.
See an example
Retrieve a list of Microsites provisioned using the Automated Certificate Management system:
```
GET /api/REST/1.0/assets/microsites?isCertificateProvisioned=true
```
For more information, see the API reference.

Bulk API

We've added the updateRuleByField parameter to Bulk API imports. This parameter specifies how Eloqua should handle updating records when you import a new value for an existing field by field. If you do not specify an updateRuleByField, or leave a field out of updateRuleByField, the rule type defaults to the rule set with updateRule. The following rule types are available:

always: Always update.
ifNewIsNotNull: Update if the new value is not blank.
ifExistingIsNull: Update if the existing value is blank.
useFieldRule: Use the rule defined at the field level.

See an example

Create a new contact import definition and set the update rule by field, for some fields.

HTTP request

POST /api/bulk/2.0/accounts/imports
							Content-Type: application/json

Request body

{
								"name": "updateRuleByField Import",
								"fields": {
								"EmailAddress": "{{Contact.Field(C_EmailAddress)}}",
								"FirstName": "{{Contact.Field(C_FirstName)}}",
								"LastName": "{{Contact.Field(C_LastName)}}",
								"Company": "{{Contact.Field(C_Company)}}",
								"Address1": "{{Contact.Field(C_Address1)}}",
								"Address2": "{{Contact.Field(C_Address2)}}",
								"City": "{{Contact.Field(C_City)}}",
								"StateProvince": "{{Contact.Field(C_State_Prov)}}"
								},
								"identifierFieldName": "EmailAddress",
								"updateRule": "always",
								"updateRuleByField": {
								"FirstName": "ifNewIsNotNull",
								"LastName": "useFieldRule",
								"Company": "ifExistingIsNull"
								}
							}

Response

{
								"name": "updateRuleByField Import",
								"updateRule": "always",
								"fields": {
								"EmailAddress": "{{Contact.Field(C_EmailAddress)}}",
								"FirstName": "{{Contact.Field(C_FirstName)}}",
								"LastName": "{{Contact.Field(C_LastName)}}",
								"Company": "{{Contact.Field(C_Company)}}",
								"Address1": "{{Contact.Field(C_Address1)}}",
								"Address2": "{{Contact.Field(C_Address2)}}",
								"City": "{{Contact.Field(C_City)}}",
								"StateProvince": "{{Contact.Field(C_State_Prov)}}"
								},
								"updateRuleByField": {
								"FirstName": "ifNewIsNotNull",
								"LastName": "useFieldRule",
								"Company": "ifExistingIsNull"
								},
								"identifierFieldName": "EmailAddress",
								"isSyncTriggeredOnImport": false,
								"dataRetentionDuration": "P7D",
								"isUpdatingMultipleMatchedRecords": false,
								"uri": "/contacts/imports/854",
								"createdBy": "API.User",
								"createdAt": "2022-02-24T23:48:28.2330000Z",
								"updatedBy": "API.User",
								"updatedAt": "2022-02-24T23:48:28.2330000Z"
							}

Learn more.

Recent changes

The new Contact Field setting "Contact Field contains valid phone number" prevents updating contact information if the contact record does not contain a valid phone number, using both Application API and Bulk API endpoints. Endpoints to update contact records are affected such as the Update a contact endpoint and Update a contact import definition. When using the Bulk API, clients with the "Reject rows that have invalid data" feature enabled will also notice that contacts will be rejected if they contain invalid phone numbers.

Application API

If there are over one million CDO (custom data object) records, the Retrieve a list of custom object data API 1.0 and 2.0 endpoints will now only accept one search request at a time if the request includes only non-indexed fields or does not include an indexed field without a leading wildcard. This limit will be per User and per Custom Object. A “429 Too Many Requests” response will be returned until the request completes.

For more information, see the product notice.

Bulk API

We have modified how Contacts are linked to Bulk API form submit activities. Eloqua will now check first for the Contact ID that was set upon form submission, and if there is not a Contact ID set upon form submission, Eloqua will then check for a Contact that’s mapped to the Visitor.

For more information, see the product notice.

Platform notices

With the arrival of Eloqua 22D release (November 2022), the EloquaService SOAP API will be deleted. For more information, see the product notice.

Documentation enhancements of note

The Mapping contacts via form submit now includes more Considerations.
We've updated the Determining base URLs tutorial to include the new pod 8.

Product notices

We have modified the Eloqua Application API endpoints used to retrieve users so that minimal depth will not return createdBy and updatedBy. For more information, see the product notice.

Release 22A

A list of developer-facing new features, significant recent changes, and platform notices for Oracle Eloqua release 22A.

New features

We've added a new property to the Form 2.0 Application API endpoints when Form Spam Protection is enabled (isFormSpamProtectionEnabled ). Learn more.

Recent changes

Bulk API

The sync logs endpoint now groups Eloqua status codes ELQ-00111 and ELQ-00121 into one message, instead of displaying multiple messages for each missing or ignored field. This enhancement reduces the number of messages reported within sync logs.

See an example

Sync logs before 22A:

{
								"items": [
								{
								"syncUri": "/syncs/2865",
								"count": 0,
								"severity": "warning",
								"statusCode": "ELQ-00121",
								"message": "Field (C_FirstName) is part of import definition, but not included in file .",
								"createdAt": "2021-10-27T23:36:34.8930000Z"
								},
								{
								"syncUri": "/syncs/2865",
								"count": 0,
								"severity": "warning",
								"statusCode": "ELQ-00121",
								"message": "Field (C_LastName) is part of import definition, but not included in file .",
								"createdAt": "2021-10-27T23:36:34.8930000Z"
								},
								{
								"syncUri": "/syncs/2865",
								"count": 0,
								"severity": "warning",
								"statusCode": "ELQ-00111",
								"message": "Field (notindeffield1) is not part of import definition, and will be ignored.",
								"createdAt": "2021-10-27T23:36:34.8930000Z"
								},
								{
								"syncUri": "/syncs/2865",
								"count": 0,
								"severity": "warning",
								"statusCode": "ELQ-00111",
								"message": "Field (notindeffield2) is not part of import definition, and will be ignored.",
								"createdAt": "2021-10-27T23:36:34.8930000Z"
								},
								{
								"syncUri": "/syncs/2865",
								"count": 0,
								"severity": "warning",
								"statusCode": "ELQ-00111",
								"message": "Field (notindeffield3) is not part of import definition, and will be ignored.",
								"createdAt": "2021-10-27T23:36:34.8930000Z"
								},
								{
								"syncUri": "/syncs/2865",
								"count": 0,
								"severity": "warning",
								"statusCode": "ELQ-00111",
								"message": "Field (notindeffield4) is not part of import definition, and will be ignored.",
								"createdAt": "2021-10-27T23:36:34.8930000Z"
								},
								{
								"syncUri": "/syncs/2865",
								"count": 0,
								"severity": "warning",
								"statusCode": "ELQ-00111",
								"message": "Field (notindeffield5) is not part of import definition, and will be ignored.",
								"createdAt": "2021-10-27T23:36:34.8930000Z"
								},
								{
								"syncUri": "/syncs/2865",
								"count": 1,
								"severity": "information",
								"statusCode": "ELQ-00130",
								"message": "Total records staged for import.",
								"createdAt": "2021-10-27T23:36:34.9870000Z"
								},
								{
								"syncUri": "/syncs/2865",
								"count": 0,
								"severity": "information",
								"statusCode": "ELQ-00137",
								"message": "Ready for data import processing.",
								"createdAt": "2021-10-27T23:36:35.0200000Z"
								},
								{
								"syncUri": "/syncs/2865",
								"count": 0,
								"severity": "information",
								"statusCode": "ELQ-00101",
								"message": "Sync processed for sync , resulting in Warning status.",
								"createdAt": "2021-10-27T23:36:35.7800000Z"
								},
								{
								"syncUri": "/syncs/2865",
								"count": 1,
								"severity": "information",
								"statusCode": "ELQ-00001",
								"message": "Total records processed.",
								"createdAt": "2021-10-27T23:36:34.6200000Z"
								},
								{
								"syncUri": "/syncs/2865",
								"count": 1,
								"severity": "information",
								"statusCode": "ELQ-00004",
								"message": "Contacts created.",
								"createdAt": "2021-10-27T23:36:35.2770000Z"
								},
								{
								"syncUri": "/syncs/2865",
								"count": 0,
								"severity": "information",
								"statusCode": "ELQ-00022",
								"message": "Contacts updated.",
								"createdAt": "2021-10-27T23:36:35.2770000Z"
								}
								],
								"totalResults": 13,
								"limit": 1000,
								"offset": 0,
								"count": 13,
								"hasMore": false
							}

Sync logs in 22A:

{
								"items": [
								{
								"syncUri": "/syncs/2865",
								"count": 0,
								"severity": "warning",
								"statusCode": "ELQ-00121",
								"message": "Field (C_FirstName,C_LastName) is part of import definition, but not included in file .",
								"createdAt": "2021-10-27T23:36:34.8930000Z"
								},
								{
								"syncUri": "/syncs/2865",
								"count": 0,
								"severity": "warning",
								"statusCode": "ELQ-00111",
								"message": "Field (notindeffield1,notindeffield2,notindeffield3,notindeffield4,notindeffield5) is not part of import definition, and will be ignored.",
								"createdAt": "2021-10-27T23:36:34.8930000Z"
								},
								{
								"syncUri": "/syncs/2865",
								"count": 1,
								"severity": "information",
								"statusCode": "ELQ-00130",
								"message": "Total records staged for import.",
								"createdAt": "2021-10-27T23:36:34.9870000Z"
								},
								{
								"syncUri": "/syncs/2865",
								"count": 0,
								"severity": "information",
								"statusCode": "ELQ-00137",
								"message": "Ready for data import processing.",
								"createdAt": "2021-10-27T23:36:35.0200000Z"
								},
								{
								"syncUri": "/syncs/2865",
								"count": 0,
								"severity": "information",
								"statusCode": "ELQ-00101",
								"message": "Sync processed for sync , resulting in Warning status.",
								"createdAt": "2021-10-27T23:36:35.7800000Z"
								},
								{
								"syncUri": "/syncs/2865",
								"count": 1,
								"severity": "information",
								"statusCode": "ELQ-00001",
								"message": "Total records processed.",
								"createdAt": "2021-10-27T23:36:34.6200000Z"
								},
								{
								"syncUri": "/syncs/2865",
								"count": 1,
								"severity": "information",
								"statusCode": "ELQ-00004",
								"message": "Contacts created.",
								"createdAt": "2021-10-27T23:36:35.2770000Z"
								},
								{
								"syncUri": "/syncs/2865",
								"count": 0,
								"severity": "information",
								"statusCode": "ELQ-00022",
								"message": "Contacts updated.",
								"createdAt": "2021-10-27T23:36:35.2770000Z"
								}
								],
								"totalResults": 8,
								"limit": 1000,
								"offset": 0,
								"count": 8,
								"hasMore": false
							}

Resolved issue that caused uploaded data to possibly be assigned to a previously created sync and cause other syncs to fail with the error "Import Sync creation aborted, there's no data to import.". This issue was only applicable when uploading data to import definitions created with isSyncTriggeredOnImport=true.

Documentation enhancements of note

We've updated the List of terms supported with search within the Using the search URL parameter tutorial.
See our new tutorial Using form spam protection with the Application API.

Release 21D

A list of developer-facing new features, significant recent changes, and platform notices for Oracle Eloqua release 21D.

Recent changes

Bulk API

We've updated the Bulk API limits. Every Eloqua instance has the following soft limits by Bulk API sync type:

Bulk API Sync Type	Limit
Export	2000 per hour
Import	2000 per hour
Sync Action	4000 per hour

There are many variables to sync processing. We'd expect minimal impact due to volume on its own if within these limits and following best practices.

Learn more about Bulk limits.

Documentation enhancements of note

We've added an example to the Using the search URL parameter tutorial, under Operators.
See the example
If including more than one different field, they will be ANDs.
?search=name='Test1'name='Test2'C_Company='Oracle'
This request will return records with a name of "Test1" or "Test2" and a Company of "Oracle".
The Sync actions page now includes a Sync Action App Status section. This section explains the sync action app statuses, the status description displayed, and when each status is set.
We've updated the Bulk API limits page to reflect the new Bulk API limits.

Release 21C

A list of developer-facing new features, significant recent changes, and platform notices for Oracle Eloqua release 21C.

New features

Application API

Asynchronous Form Processing via API is now available for the Create form data for a single form endpoint. Learn more.

Authentication

More detailed 401 error responses are now available when authenticating with OAuth 2.0:
- For the https://login.eloqua.com/auth/oauth2/token endpoint, for the error code "401 Unauthorized", the response body will now include an error, error code, and error description. For example:
```
{
								"error": "unknown_token",
								"error_code": 2501,
								"error_description": "Provided Token is Unknown."
							}
```
  Here's a description of each property:
  - error: The name of the error type.
  - error_code: The numeric value uniquely identifying the type of error.
  - error_description: Provides details on the error.
- Errors have been divided into categories indicated by the 1000s digit of the error_code according to the following:
  - 1000: General Error Messages
  - 2000: Error Messages Related to Authentication
  - 2500: Error Messages Related to OAuth2.0 Authentication
  - 3000: Error Messages Related to Authorization

For more information see the product notice, or refer to the documentation.

Bulk API

Update August 27th 2021: This feature is no longer included in 21C.

Bulk API imports now accept json encoded in surrogate pairs, e.g. \uD83D\uDE03.
When an external ID is used as the identifierFieldName for imports, the Bulk API will now extract the ID and match on the ID. This change improves the performance of imports. The following external IDs are extracted and matched:
```
{{Contact.Field(ContactIDExt)}}
						{{Account.Field(CompanyIDExt)}}
						{{CustomObject[<id>].ExternalId}}
					{{Event[<id>].ExternalId}}
```

Recent changes

App Developer Framework

When there is no response to the Notification URL call from the App, Eloqua will now retry the Notification URL call over approximately an eight-hour period of time instead of failing after one attempt
For Content services, Eloqua will now set records to "error" as soon as errors occur. Previously there was a 24 hour delay.

Bulk API

Resolved an issue where the createdAt timestamp in the Create sync endpoint response was not matching the createdAt timestamp in the Retrieve a sync endpoint response.
We have added an improved retry strategy to cover a wider variety of failures that can occur during Bulk API export.

Platform notices

Oracle will be modifying its supported cipher suites used for Transport Layer Security (TLS) connections to Eloqua. This includes programmatic access to Eloqua via APIs. Additional Ciphers were added on August 1, 2021 and weak Ciphers will be removed on October 1, 2021, providing customers with a 2 month window for testing in between. For more information see the product notice.

Documentation enhancements of note

We've added a new tutorial that explains how using the Multiple Branded Domains feature changes the way you interact with the Application API endpoints. See Using multiple branded domains with the application API for more information.

Release 21B

A list of developer-facing new features, significant recent changes, and platform notices for Oracle Eloqua release 21B.

New features

Application API

The default depth for the Application API Retrieve batch form submission details endpoints has been changed to minimal (previously, the default depth was complete). For more information, see the product notice.

App Developer Framework

CampaignId has been added as a URL template parameter to the Content Service Landing Page Notification URL. The CampaignId will be populated with the elqCampaignId query parameter.

Recent changes

Application API

Updating a value for custom field which is set to uniqueCode on Custom Object will now assign value to uniqueCode for the Custom Object record.
A validation error has been added for the Custom Object endpoints, so that an error is returned if the same field is included more than once.

App Developer Framework

The following new app member status has been added "Import Queued by App". This message is displayed when an App has created an import to update a step member's status. See the Oracle Eloqua Help Center for a list of all the different status messages you can see related to app members moving through your campaigns and programs.

Bulk API

Emails sent from the Outlook Plugin are now displayed as OutlookPlugin for the EmailSend Type in Bulk API activity exports.
Bulk API dependencies now appear when there is a Bulk API event definition.
We have added an improved retry strategy to cover a wider variety of failures that can occur during Bulk API export.

Platform notices

With the arrival of Eloqua Release 21C, Asynchronous Form Processing via API will be released for the Create form data for a single form endpoints. This feature can be enabled for Early Preview with Eloqua Release 21B.

Release 21A

A list of developer-facing new features, significant recent changes, and platform notices for Oracle Eloqua release 21A.

New features

Application API

We've added a new endpoint that enables you to retrieve spam form submissions. A successful response will return a list of all spam form submissions for the form. This endpoint is released under our Controlled Availability program. Please contact your account representative for more information. For more information about the endpoint, see the API Reference.

Bulk API

We've added a new campaign response field {{CampaignResponse.AddedAt}}. This new field enables you to determine the date and time campaign responses were added to your Eloqua database, when creating campaign response export definitions. The Bulk API Campaign Response export will now use AddedAt instead of CreatedAt when enforcing the 30 day limit of campaign responses you can retrieve.

Recent changes

Application API

Validation has been added to the Application API endpoint to Update a contact field to disallow changing a contact field from Text box, Check box, or Single-select list to a Multi-select list.

App Developer Framework

The status message "Eloqua configuration error – Manage Data Export Permission" has been updated to allow the app to set this status. App developers can set this status for Action and Decision services using sync actions or export filters. Previously this could only be set by Eloqua if records were set to be returned in the Notify call. See the Oracle Eloqua Help Center for a list of all the different status messages you can see related to app members moving through your campaigns and programs.
See an example of setting the new permission status with a sync action
{ "action": "setStatus", "destination": "{{ActionInstance(f82d50cd86a94fcab37e4ec9a98b0339).Execution[12345]}}", "status": "permission", "updateAll": true }
We have improved the App Developer Notification call, by adding a retry strategy to cover a wider variety of failures that can occur with sending notification calls.

Documentation enhancements of note

We've added new notes for multiple Eloqua status codes to better help you troubleshoot.

Release 20D

A list of developer-facing new features, significant recent changes, and platform notices for Oracle Eloqua release 20D.

New features

Application API

Batch processing of forms via API is now generally available. This allows you to create API Form Submission payloads in batches of 500. For more information, see the API Documentation.
We've made the following enhancements to the Email endpoints to support email archiving:
- There are two new API endpoints to enable archiving and unarchiving emails. For more information, see the API Documentation.
  See an example
  Archive an email with the email ID 5 into the folder with the folder ID 10:
  
  POST/api/REST/2.0/assets/email/5/archive { "targetFolderId": "10" }
- The Update an email endpoints in 1.0 and 2.0 has new validation to prevent updating archived emails.
- The Retrieve a list of emails endpoints in the Application API 1.0 and 2.0 now only returns unarchived emails by default.
- Two new query parameters are available with the Retrieve a list of emails endpoint in the Application 2.0 endpoint: includeAvailable and includeArchived. These new query parameters enable you to filter archived emails. For more information, see the API Documentation.
  See an example
  Retrieve archived emails:
  
  GET /api/REST/2.0/assets/emails?includeAvailable=false&includeArchived=true
- The archive property has been renamed to archived. For more information, see the product notice.

We've added support for the new type EmailInlineDeployment with the Email Deployment endpoint to enable sending HTML emails, instead of having to specify an existing Eloqua email, as well as being able to schedule email deployments using the sendDate parameter. Emails can be sent to up to 2000 contacts per request.

For more information, see the API Documentation.

A new property, crmSystemMappings, is now returned at complete depth with the Retrieve an account Application API endpoint. This property is returned when the Account is linked to an Eloqua User, and indicates the CRM User Names and Eloqua Login Name for each Eloqua User linked to the Account. For more information, see the product notice.

Bulk API

You can now use the Bulk API Account Import to link Eloqua Users to Accounts. By specifying a CRM User Id, you can create a link between Eloqua Users and Accounts to be used by integrations.

When creating a Bulk API sync, the definition will now be validated. We've also added a new sync log message to inform you if syncs fail because of a temporary error. For more information, see the product notice.

Recent changes

App Developer Framework

We’ve added two new app member statuses, one surfaces when the Eloqua User does not have access to Export records, and the other displays when the app step is waiting for the scheduled send period. Additionally, the “Invalid app configuration” status has been updated to include when the export fails because of an invalid definition. See the Oracle Eloqua Help Center for a list of all the different status messages you can see related to app members moving through your campaigns and programs.

Application API

A new URL query parameter, ownedByUserID, is now available for the Retrieve an account endpoint endpoint. Set this query parameter to an Eloqua User Id to return all Accounts linked to that Eloqua User. Example: This request will return all Accounts linked to Eloqua User Id 71:

GET /api/REST/1.0/data/accounts?ownedByUserID=71

Bulk API

A new retention policy is now in effect for Bulk API syncs including sync logs and rejects (older than one year). This new retention policy will continue to be applied from 20D on. For more information, see the product notice.

Documentation enhancements of note

We've added a new topic that details how to import account data.

Product Notices

Oracle modified its supported cipher suites used for Transport Layer Security (TLS) connections to Eloqua. This includes programmatic access to Eloqua via APIs. This change has been rolled back. For more information, see the product notice.

Release 20C

A list of developer-facing new features, significant recent changes, and platform notices for Oracle Eloqua release 20C.

New features

You can now write to the "Last Modified by CRM" system field for Contacts and Accounts. This enhancement enables developers of CRM integrations to indicate when a Contact and Account has been updated by CRM.

Application API

We've added new Application 2.0 API endpoints that enable you to manage Users. Along with managing Users, these new endpoints enable you to perform actions that are not available in 1.0 such as Enable or Disable a User and Update a User's Password. For more information, see the API Documentation.
We've added new API endpoints that enable you to manage Eloqua Security Groups. For more information, see the API documentation.

Recent changes

App Developer Framework

We've updated our retry strategy when Eloqua calls an App's Notification URL. Eloqua will now retry the Notification URL call over approximately an eight-hour period of time with a backoff strategy. See the product notice to learn more.
We've implemented new detailed status messaging for stuck records. The following new app member statuses have been added:
- Awaiting app to process: App Service Settings Step Response is set to None
- Authentication required - Reinstall app: App does not have a valid token
- Invalid app configuration: App sets status to invalid
- Eloqua notifying app: Eloqua is calling the app's Notification URL
- Being processed by app: This status used to be Being processed by external service
- Eloqua failed to notify app: All of Eloqua's calls to app's Notification URL have failed. Will be routed to error path.
- Status Error set by Eloqua: There was an Eloqua error that was not related to an invalid definition. Will be routed to error path.
- App notified successfully - Awaiting app to process: Eloqua received 200 level response to the Notification URL from the app (when Service Setting of Records per Notification is set to 0)
- Status 'Error' set by app: App sets status to error. Will be routed to error path.
We've added new validation to ensure app service instances exist, and in cases where service instances do not exist, a validation error will be returned. This validation applies when creating or updating import and export definitions, creating syncs, and executing syncs.
- See an example
  Here's an example where a validation error is returned when attempting to create or update a definition referencing an app service instance ID that does not exist.
  
  { "failures": [ { "field": "filter", "value": "STATUS('{{ActionInstance(2a9f17e8ca374447a8e6ceb24ccd246)}}') = 'pending'", "constraint": "Must be a reference to an existing object." } ] }

Application API

The Contact Field endpoints no longer return the isPopulatedInOutlookPlugin property. See the product notice for more information.

Platform notices

With the arrival of Eloqua release 20D (Nov 2020), we will begin applying a new retention policy on Bulk API syncs, including sync logs and rejects, that are older than one year. This new retention policy will continue to be applied from 20D onwards. For more information, see the product notice.

Documentation enhancements of note

We've added a new topic that explains app statuses. See the Oracle Eloqua Help Center for a list of all the different status messages you can see related to app members moving through your campaigns and programs.

Release 20B

A list of developer-facing new features, significant recent changes, and platform notices for Oracle Eloqua release 20B.

New features

Application API

We've added new API endpoints to enable you to archive and unarchive forms programmatically. Archiving forms enables you to hide older forms from search, choosers, and newer marketing activities. Forms in archive can still accept form submissions, but cannot be edited, copied or used in new campaigns or content.

A new property has been added to the Forms API endpoints in 1.0 and 2.0. The archived property is a boolean which indicates whether or not a form is in archive.

The Update a form endpoints will have new validation to prevent updating archived forms, and we've also made changes to the Retrieve a list of forms endpoints. Retrieve a list of forms endpoint will only return unarchived forms by default. Two new URL parameters will be available with the Retrieve a list of forms endpoint: includeAvailable and includeArchived, which will enable filtering results on the archived state.

For more information, see the product notice and API documentation.

Bulk API

We've added a new activity field named FormSubmitSavedId. This field is available when creating an activity export definition for form submit activity types. This new activity field enables you to include the identifier of when form submissions were saved in your form submit activity reports, so you can export form submit activities periodically without missing any.

The syntax is:
- FormSubmitSavedId: {{Activity.Field(FormSubmitSavedId)}}
When export data is retrieved, the FormSubmitSavedId will be populated with the unique identifier for when the form submission was saved.
See an example
Here's sample export data that includes FormSubmitSavedId:
{ "ActivityId": "234", "ActivityType": "FormSubmit", "ActivityDate": "2018-08-09 09:04:13.010", "AssetType": "Form", "AssetName": "Form Test", "AssetId": "3", "RawData": "firstName=Text&lastName=&annualRevenue1=&emailAddress=&country=&leadStatus1=&leadScoreExplicit1=&salesperson=&multipleSelectMenu=&submit=", "FormSubmitSavedId": "20", "ExternalId": "FSDC13000000000234", }

Recent changes

App Developer Framework

Resolved an issue related to receiving content from an app to improve consistency of content services.

Authentication

If the current access token has not been used, submitting a request to authenticate with the previous refresh token will now return the existing new access token and refresh token. This update alleviates the need to have to reinstall an app if there is a server error during token refresh.

Bulk API

Resolved an issue where it was possible to create custom object export definitions that included a contact lead scoring field, even though contact lead scoring fields are not supported in custom object exports, and the sync would always fail. Now, creating a custom object export definition that includes a contact lead scoring field will result in a 400 validation error.

We've added a new, more detailed error message for 500 error responses to Bulk API requests. The new error response indicates the type of error, error severity, and when users should retry the request.
- error: Describes the type of error.
- errorSeverity: The severity of the error ranging from 3, 2, 1, and 0. 0 being the highest.
- Retry-After: Based on the error severity, indicates in seconds when the request should be retried.
This new error message provides Bulk API users with more information regarding failed requests, and guidance on when to retry requests.

For more information, see the product notice.
See an example
500 The service has encountered an error. Retry-After: 120 { "error": "Unable to process request due to a temporary error", "errorSeverity": 3 }
In certain cases where an export sync attempt fails but Eloqua will retry, Eloqua will now return a message indicating Eloqua will retry the sync. The new status code ELQ-00145 indicates your sync will be retried, and the message indicates when Eloqua will retry the sync. For more information, see the product notice.
See an example
{ "syncUri": "/syncs/2651", "count": 0, "severity": "information", "statusCode": "ELQ-00145", "message": "Sync attempt failed. The sync will be retried in X seconds.", "createdAt": "2020-03-01T22:45:55.1570000Z" }

Platform notices

With the arrival of Eloqua release 20D (Nov 2020), we will begin applying a new retention policy on Bulk API syncs, including sync logs and rejects, that are older than one year. This new retention policy will continue to be applied from 20D onwards. For more information, see the product notice.

Documentation enhancements of note

Added a list of search terms per endpoint to the Using the search URL parameter tutorial, to provide guidance on which terms to use when searching using the Application API.

Release 20A

A list of developer-facing new features, significant recent changes, and platform notices for Oracle Eloqua release 20A.

New features

Application API

accountId will now be returned at complete depth when retrieving, creating, or updating Contacts using the Application API when the Contact is linked to an Account. For more information, see the product notice.

Bulk API

You can now set the status for all records in an execution using just the execution ID. The new updateAll parameter determines what status to set records in an execution, when creating a contact or custom object sync action definition.

Recent changes

Application API

As part of the Classic Design Editor changes, the Create a form Application API Form endpoints will not allow you to create classic design editor forms and Update a form Application API endpoints will not allow changing a form from responsive to classic. Review the Product Notice for further information and schedule changes.

Bulk API

Resolved an issue where it was possible to create export definitions with a dataRetentionDuration of null, resulting in data being deleted sooner than intended. Now, dataRetentionDuration can no longer be set to null, and the default duration will continue to be 12 hours (ie. PT12H).

Platform notices

Resolved an issue where it was possible to create export definitions with a dataRetentionDuration of null, resulting in data being deleted sooner than intended. Now, dataRetentionDuration can no longer be set to null, and the default duration will continue to be 12 hours (ie. PT12H).

Release 19D

A list of developer-facing new features, significant recent changes, and platform notices for Oracle Eloqua release 19D.

New features

Application API

We've added new ways you can filter landing pages when using the Retrieve a list of landing pages endpoint:

Filter by content source: You can now search for landing pages by content source using the new query parameter contentSource, specifying content source by ID:

editor = 0
upload = 1
migration = 2
responsive = 3

We recommend always using the Application 2.0 API endpoints, as some functionality may not be available in 1.0. The Application 1.0 endpoint cannot retrieve responsive landing pages.

Filter by vanity URL: You can now search for landing pages by the landing page's vanity URL, also known as the relativePath. After 19D, using the search URL parameter with name will include matches for landing page name and relativePath.

Note: To search on both the name and relativePath, the leading wildcard “*” is required as the relativePath always starts with a “/”.

Example

GET /api/REST/2.0/assets/landingPages?search=name=*My_Landing_Page

GET /api/REST/2.0/assets/landingPages?search=*My_Landing_Page

Response body:

{
											"elements": [
											{
											"type": "LandingPage",
											"currentStatus": "Draft",
											"id": "4699",
											"createdAt": "1568155254",
											"createdBy": "71",
											"depth": "minimal",
											"folderId": "1265",
											"name": "search_name_and_relativePath",
											"permissions": [
											"Retrieve",
											"SetSecurity",
											"Delete",
											"Update"
											],
											"updatedAt": "1568155289",
											"updatedBy": "71",
											"excludeFromAuthentication": "false",
											"htmlContent": {
											"type": "RawHtmlContent",
											"contentSource": "upload"
											},
											"relativePath": "/relative_path"
											},
											{
											"type": "LandingPage",
											"currentStatus": "Draft",
											"id": "4700",
											"createdAt": "1568155393",
											"createdBy": "71",
											"depth": "minimal",
											"folderId": "1265",
											"name": "Landing_Page_Name",
											"permissions": [
											"Retrieve",
											"SetSecurity",
											"Delete",
											"Update"
											],
											"updatedAt": "1568155393",
											"updatedBy": "71",
											"excludeFromAuthentication": "false",
											"htmlContent": {
											"type": "RawHtmlContent",
											"contentSource": "upload"
											},
											"relativePath": "/search_name_and_relativePath"
											}
											],
											"page": 1,
											"pageSize": 1000,
											"total": 2
										}

Filter by user who created or last updated the landing page: Use the search URL parameter with the updatedByUserId or createdByUserId properties to filter landing pages.

The Retrieve a list of landing pages API endpoint will now return a landing page's vanity URL (relativePath) at minimal depth. For more information, see the product notice.

You can now search for forms by content source using the new query parameter contentSource, specifying content source by ID:

classic forms = 0
responsive forms = 3

Note that you must specify the content source ID to search.

Recent changes

Application API

We've modified the Retrieve a list of activities endpoint so that an email DeploymentId now appears in the response for emailOpen, emailSend, and emailClickThrough activity types. The DeploymentId allows email activities to be associated with a specific deployment. For more information, see the product notice.
We've made changes to the Landing Pages endpoints so that minimal depth will return relativePath, and using the search URL parameter with name when retrieving a list of landing pages will return matches for name and relativePath. For more information, see the product notice.
The Form endpoints will now return htmlName at minimal depth. For more information, see the product notice.

Bulk API

Resolved an issue where creating activity export definitions and setting maxRecords would correctly create the definition and respect the maxRecords property, however the maxRecords property was not appearing when creating or retrieving the definition. The maxRecords property now appears as expected in these scenarios.
Resolved an issue where creating a Bulk API import with the contact fields {{Contact.Email.IsSubscribed}} and {{Contact.Email.IsBounced}} would result in an incorrect email status. This issue has been resolved.

Platform notices

The Classic Design Editor changes are coming in our 20A release (February 2020). Review the Product Notice for further information and schedule changes.

Documentation enhancements of note

The new Bulk API Best Practices section has become a growing list of best practices when using the Bulk API, such as reusing definitions and how to best retrieve data.

Release 19C

A list of developer-facing new features, significant recent changes, and platform notices for Oracle Eloqua release 19C.

New features

Application API

Added a new endpoint that enables you to retrieve visitor data by visitor GUID, aka externalId. This endpoint differs from the existing Retrieve visitor data endpoint, because it is a POST request that can include up to 200 visitors per request. Learn more

The Application API Email endpoints have been updated so that minimal depth will now return the subject property (the email's subject line). Additionally, using the search URL parameter with name when retrieving a list of emails, will return matches for name and subject. Learn more

We've added new query parameters for the Retrieve a list of emails endpoint.

updatedByUserId - Filters emails by the user ID who last updated the email asset.
createdByUserId - Filters email by the user ID who created the email asset.

See the tutorial for more information about searching.

You can now search for emails by content source using the new query parameter contentSource, specifying content source by ID:

editor = 0
upload = 1
responsive = 3

Note that you must specify the content source ID to search.

See the tutorial for more information about searching.

Bulk API

We've added two new activity fields related to campaign responses:

{{Activity.CampaignResponse.CreatedAt}} - The date and time the campaign response was created.
{{Activity.CampaignResponse.Field(MemberStatus)}} - The status of the campaign member.

These new fields enable retrieving campaign response fields with exported activities to analyze campaign response data. These activity fields are available for the Email Open, Email Clickthrough, Email Send, Page View, and Form Submit activity types.

Recent changes

Application API

All API endpoints for emails and landing pages no longer allow creating and editing classic emails and landing pages. When attempting to create or edit a classic email or landing page, the following error will be returned:
```
'410 htmlContent type of StructuredHtmlContent (Classic editor) is no longer supported.'
```
For more information about the classic editor sunset, see the Email and Landing Page product notice
Oracle modified its supported cipher suites used for Transport Layer Security (TLS) connections to Eloqua. This includes programmatic access to Eloqua via APIs. Learn more

Bulk API

We've modified how Contacts are linked to Bulk API form submit activities, by setting the Contact that’s mapped to the Visitor, if there is a Visitor record linked to the form submit activity. For more information, see the product notice.
Resolved an issue where a Bulk API sync action to globally subscribe a contact was resulting in the contact not appearing in Eloqua's Segment's UI when filtered by date criteria.

Platform notices

We have revised the dates of the sunsetting of some functionality of our Classic Form Design Editor. While originally we had communicated you would no longer be able to edit or create new forms with the Classic editor as of 19C (August 2019), we have adjusted the date to our 20A release (February 2020). Please review the updated Product Notice for further information and additional schedule changes.

Release 19B

A list of developer-facing new features, significant recent changes, and platform notices for Oracle Eloqua release 19B.

New features

Application API

Asynchronous form processing via API is released under our Controlled Availability program. You can request access to this feature by submitting a request to My Oracle Support. A future product notice will provide details.
A new property has been added to the Application 1.0 and 2.0 Custom Objects API endpoints. The deleteLinkedCustomObjectData property is a boolean that determines whether or not custom object records are deleted when linked contact records are deleted. Does not apply to records that are unmapped or account deletion. Deleting records is irreversible and data cannot be recovered. The default value is false. This feature is released under our Controlled Availability program. You can request access to this feature by submitting a request to My Oracle Support.

Bulk API

We’ve added two new activity fields: WebVisitSavedId and PageViewSavedId. WebVisitSavedId is available when creating an activity export definition for web visit activity types to include the id of when web visits were saved. PageViewSavedId is available when creating an activity export definition for page view activity types to include the id of when page views were saved. You can use the new activity fields in the activity export definition filter to successfully export web visit and page view activities periodically without missing any.

The syntax for the new activity fields:
- WebVisitSavedId: {{Activity.Field(WebVisitSavedId)}}
- PageViewSavedId: {{Activity.Field(PageViewSavedId)}}
When export data is retrieved, the WebVisitSavedId will be populated with the unique identifier for when the web visit was saved, and PageViewSavedId will be populated with the unique identifier for when the page view was saved.
See an example
Here's sample export data that includes WebVisitSavedId:
{ "ActivityId": "2147573510", "ActivityType": "WebVisit", "ActivityDate": "2018-01-19 04:20:58.517", "ContactId": "1659305", "VisitorId": "5269", "VisitorExternalId": "", "IpAddress": "139.130.4.5", "WebVisitSavedId": "6110" }

Recent changes

Application API

As part of the Classic Design Editor Sunset, the API endpoints will not allow you to create classic emails and landing pages (request body for htmlContent with a type of StructuredHtmlContent). However, you can still use the API to edit emails and landing pages. Any new emails and landing pages created using the API endpoints should have a request body for htmlContent with a type of RawHtmlContent. If this is not specified, the API endpoints will still default to creating new emails and landing pages with RawHtmlContent.

Creating emails or landing pages with the htmlContent type ResponsiveHtmlContent is not supported. If you use the ResponsiveHtmlContent type, we cannot guarantee your email or landing page will be responsive.

As of release 19C, all API endpoints for emails and landing pages will not allow creating and editing classic emails and landing pages. Classic forms will still be allowed to be edited through release 20A, but no new classic forms will be allowed to be created starting in 19C. Any forms created or updated with the API endpoints will need to be responsive starting in 19C. A future product notice will provide details on usage.

For more information about the classic editor sunset, see the Email and Landing Page product notice and the Form product notice.
A new property, isHidden, that stores the “Form Visibility” form setting, was added to the Application API Form endpoints. For more information, see the product notice.

Bulk API

Resolved an issue where performing an activity export for Subscribe, Unsubscribe, and Bounceback activity types using the statement {{Activity.Field(EmailAddress)}} could result in email addresses being returned in a case different than the case set on the contact currently. Performing an activity export for these activity types, and using this statement, will now return email addresses in the current case of the contact.

Resolved an issue where creating an activity import sync and then syncing invalid data to the import definition would result in the sync status being active instead of error.

Optimizations have been made to Bulk API custom object imports that include a large number of fields and records.
Bulk API Contact export definitions with an EXISTS() Segment filter, e.g. EXISTS('{{ContactSegment[<id>]}}'), will only allow up to two system updated or created date criterion. For more information, see the product notice.

Platform notices

As of release 19C, all API endpoints for emails and landing pages will not allow creating and editing classic emails and landing pages. Classic forms will still be allowed to be edited through release 20A, but no new classic forms will be allowed to be created starting in 19C. Any forms created or updated with the API endpoints will need to be responsive starting in 19C. A future product notice will provide details on usage.

For more information about the classic editor sunset, see the Email and Landing Page product notice and the Form product notice.
With the arrival of Eloqua release 19C (Aug 2019), Oracle will be modifying its supported cipher suites used for Transport Layer Security (TLS) connections to Eloqua. This includes programmatic access to Eloqua via APIs. Learn more

Release 19A

A list of developer-facing new features, significant recent changes, and platform notices for Oracle Eloqua release 19A.

New features

Application API

Added a new Audit Log API endpoint to initiate an Eloqua audit log export using the Application API. This API endpoint enables you to specify the type of audit log you want to export within a specified date and time range. If the request is successful, a report will be sent to the email address specified in the request. Previously, initiating audit log exports were only accessible in Eloqua or using an SFTP server after exporting. Learn more
Example
Initiate an audit log export for campaign assets for all actions:
POST /api/REST/2.0/data/auditLog/reportExport Content-Type: application/json
Request
{ "auditReportType": "Assets", "startDate": "1546837200", "endDate": "1547528400", "notificationEmail": "API.User@test.com", "fileFormat": "DelimitedFile", "assetTypes": "Campaigns", "actionName": "all" }
Response
201 Created
If the request is successful, the exported audit log is sent to the email address specified by notificationEmail.
A new property has been added to the Contact Fields API endpoints. The showTrustedVisitorsOnly property is a boolean that determines whether or not a contact field is displayed only to trusted visitors. A trusted visitor is a contact who has undergone an additional form of verification. A contact field where this property is set to true will only be displayed to trusted visitors.

For more information, see the Oracle Eloqua Help Center.

Bulk API

We've added a new activity field that enables you to filter on the date and time a visitor was linked to a contact. This activity field is available when creating an activity export definition for page view or web visit activity types. Activity records are only returned when linked to a contact. Previously, to export all newly linked activity records, an export as far back as an activity is meaningful would need to be performed to capture newly linked records. With LinkedToContactDate, newly linked activity records can efficiently be exported without exporting activities that have already been exported.

The syntax for the new LinkedToContactDate activity field is: {{Activity.Field(LinkedToContactDate)}}

When export data is retrieved, the LinkedToContactDate will be populated with the date and time the contact was linked to a visitor.
See an example
Here's sample export data that includes LinkedToContactDate:
{ "ActivityId": "2147573510", "ActivityType": "PageView", "ActivityDate": "2018-01-19 04:20:58.517", "ContactId": "1659305", "VisitorId": "5269", "VisitorExternalId": "", "WebVisitId": "6448", "Url": "http://microsites.eloqua.com/LP=1?PURLCode=&optin=all&DisplayBanner=1&elqTrackId=xxxxxxxxxxxxx&elqaid=8604&elqat=1&elqCampaignId=&elq=xxxxxxxx", "ExternalId": "ABC1P3002147573510", "LinkedToContactDate": "2017-10-04 05:56:33.177", "EmailAddress": "API.User@oracle.com", "ContactIdExt": "CM1P3000001659305" }

Recent changes

Oracle Eloqua deprecated TLS 1.1 on January 18, 2019. Learn more

Application API

Resolved an issue with the Application 2.0 Custom Object API endpoints where retrieving and updating a custom object with a custom object field name greater than 50 characters would truncate the name value to 50 characters in the response. With release 19A, if the custom object field name is greater than 50 characters, there will be a validation error.
The API endpoint to retrieve a list of activities will now only return EmailContent when depth is set to complete. The default depth for this endpoint is complete, and remains unchanged. Set the depth to minimal in the request URL to have EmailContent not returned. See Request depth for details on setting depth.
Resolved an issue where using the Application 1.0 Accounts API endpoint to find matching accounts based on a search parameter would not return all of the account fields in the response.
The ability to mark forms as internal so that form submissions are dropped, is now available in Controlled Availability. This feature includes the addition of a new property to the Form API endpoints. You can request access to this feature by submitting a request to My Oracle Support.

Bulk API

Resolved an issue where creating an activity export definition with ReferrerUrl in the filter would cause the export sync to fail. With release 19A, a validation error will be returned if trying to use ReferrerUrl in the filter of a page view export definition.
The Campaign Response endpoints are now Generally Available. These endpoints enable developers to access campaign responses, to support the specific use case of updating a campaign response status in CRM via an App on Program or Campaign Canvas. These endpoints can only be used by an App service instance selected in Response Rules setup, and cannot be accessed otherwise. With this feature, the Campaign Responses Data Source for listeners will also be Generally Available.

You can learn more about Campaign Responses by reading the tutorial or referring to the API documentation.
Resolved an issue where a Bulk API import that did not include C_EmailAddress within fields and isUpdatingMultipleMatchedRecords was set to true, did not successfully update matching records.

Platform notices

The API endpoints for emails, landing pages, and forms are undergoing changes in releases 19B and 19C as part of the Classic Design Editor Sunset.

As of release 19B, the API endpoints will not allow you to create classic emails and landing pages (request body for htmlContent with a type of StructuredHtmlContent). However, you can still use the API to edit emails and landing pages. Any new emails and landing pages created using the API endpoints should have a request body for htmlContent with a type of RawHtmlContent. Creating emails or landing pages with the htmlContent type ResponsiveHtmlContent is not supported. If you use the ResponsiveHtmlContent type, we cannot guarantee your email or landing page will be responsive. For the forms API endpoints, you will still be able to use the API to create and update classic forms.

As of release 19C, all API endpoints will not allow creating and editing classic emails, landing pages, or forms. Any forms created with the API endpoints will need to be responsive. A future product notice will provide details on usage.

For more information about the classic editor sunset, see the product notice.

Documentation enhancements of note

We've added a new tutorial that explains how to use the Campaign API endpoints to create a detailed campaign with steps. Learn more
There's a new campaign element reference page. This topic lists the JSON objects needed to create campaign steps when creating campaigns using the Campaigns API endpoints. Learn more

Release 18D

A list of developer-facing new features, significant recent changes, and platform notices for Oracle Eloqua release 18D.

New features

Application API

You can now use the Landing Pages Application API 2.0 endpoints to create, update, retrieve, and delete landing pages. Learn more
You can now use the Forms Application API 2.0 endpoints to create, update, retrieve, and delete forms. Learn more
You can now use the Form Data Application API 2.0 endpoints to create, retrieve, and delete form data. Learn more

Recent changes

Authentication

Resolved an issue where calls to Eloqua's OAuth 2.0 token endpoint would return an empty response body if there was an error with the request. Errored requests made to Eloqua's OAuth 2.0 token endpoint will now return a detailed message. The token endpoint is https://login.eloqua.com/auth/oauth2/token.
We modified the Eloqua OAuth 2.0 authorization flow initiation to only accept one initiation per minute for any given user of an app. For more information, see the product notice on Topliners.

Application API

The processingStepErrors property has been added to the response to submitting a form using the Application 1.0 and 2.0 endpoints. This property was previously in Early Preview status in Release 18C. This property provides more detailed information about form processing step errors. For more information, see the product notice on Topliners.

A new form field validation property has been added to the Application 2.0 Form endpoints called PreventXSSCondition. This field validation is being added to prevent form data from being saved if HTML is present in a field. For more information, see the product notice on Topliners.

The requirement property has been added to the response when submitting form data with invalid values using the Application 1.0 and 2.0 endpoints. This property provides more information about invalid form data being submitted to a form field. See the Eloqua Help Center for more information about form field validation.

Example: Submitting form data

Submit form data when a field with IsDateCondition validation contains an invalid value:

POST /API/REST/2.0/data/form/4
								Content-Type: application/json

Request body:

{
									"type": "FormData",
									"fieldValues": [
									{
									"type": "FieldValue",
									"id": "2",
									"name": "emailAddress",
									"value": "jon.doe@gmail.com"
									},
									{
									"type": "FieldValue",
									"id": "4",
									"name": "leadScoreDateMostRecent1",
									"value": "xyz"
									}
									]
								}

Response prior to 18D:

[
									{
									"type": "ObjectValidationError",
									"container": {
									"type": "ObjectKey",
									"objectType": "FormData"
									},
									"property": "1",
									"value": " xyz "
									}
								]

Response after 18D:

[
									{
									"type": "ObjectValidationError",
									"container": {
									"type": "ObjectKey",
									"objectType": "FormData"
									},
									"property": "4",
									"requirement": {
									"type": "DateRequirement"
									},
									"value": "xyz"
									}
									]

The response indicates the value "xyz" does not meet the DateRequirement condition.

Resolved an issue where a campaign import could modify the end date of a campaign that is Completed or Active, causing campaigns to end before the intended end date. Campaign imports will no longer be able to modify the end date of campaigns that are Completed or Active.
As mentioned in the Eloqua 18C changelog, the resendLimit property introduced in 18A was removed from the processingSteps type FormStepSendEmail for Application API Form endpoints. For more information, see the product notice on Topliners.
As mentioned in the Eloqua 18C changelog, the Create an external activity Application API endpoint will no longer create External Asset Types or External Activity Types if they do not exist. A new Action Permission, “Register External Activities”, is required to use the Create an external activity Application API endpoint. Learn more

Bulk API

You can now include Contact.Id for Bounceback, Subscribe, and Unsubscribe activity export definitions. This enhancement enables developers to include Contact.Id on export definitions for all activity types.

Example: Create an activity export

Create a bounceback activity export definition:

POST /api/bulk/2.0/activities/exports
								Content-Type: application/json

Request body:

{
									"filter": "'{{Activity.Type}}'='Bounceback'",
									"name": "Bulk Activity Export - Bounceback",
									"fields": {
									"ActivityId": "{{Activity.Id}}",
									"ActivityType": "{{Activity.Type}}",
									"ActivityDate": "{{Activity.CreatedAt}}",
									"EmailAddress": "{{Activity.Field(EmailAddress)}}",
									"ContactId": "{{Activity.Contact.Id}}",
									"AssetType": "{{Activity.Asset.Type}}",
									"AssetName": "{{Activity.Asset.Name}}",
									"AssetId": "{{Activity.Asset.Id}}",
									"CampaignId": "{{Activity.Campaign.Id}}",
									"CRMCampaignId": "{{Activity.Campaign.Field(CRMCampaignId)}}",
									"CampaignName": "{{Activity.Campaign.Field(CampaignName)}}",
									"ExternalId": "{{Activity.ExternalId}}",
									"EmailRecipientId": "{{Activity.Field(EmailRecipientId)}}",
									"DeploymentId": "{{Activity.Field(EmailDeploymentId)}}",
									"SmtpErrorCode": "{{Activity.Field(SmtpErrorCode)}}",
									"SmtpStatusCode": "{{Activity.Field(SmtpStatusCode)}}",
									"SmtpMessage": "{{Activity.Field(SmtpMessage)}}"
									}
								}

Request response:

{
									"name": "Bulk Activity Export - Bounceback",
									"fields": {
									"ActivityId": "{{Activity.Id}}",
									"ActivityType": "{{Activity.Type}}",
									"ActivityDate": "{{Activity.CreatedAt}}",
									"EmailAddress": "{{Activity.Field(EmailAddress)}}",
									"ContactId": "{{Activity.Contact.Id}}",
									"AssetType": "{{Activity.Asset.Type}}",
									"AssetName": "{{Activity.Asset.Name}}",
									"AssetId": "{{Activity.Asset.Id}}",
									"CampaignId": "{{Activity.Campaign.Id}}",
									"CRMCampaignId": "{{Activity.Campaign.Field(CRMCampaignId)}}",
									"CampaignName": "{{Activity.Campaign.Field(CampaignName)}}",
									"ExternalId": "{{Activity.ExternalId}}",
									"EmailRecipientId": "{{Activity.Field(EmailRecipientId)}}",
									"DeploymentId": "{{Activity.Field(EmailDeploymentId)}}",
									"SmtpErrorCode": "{{Activity.Field(SmtpErrorCode)}}",
									"SmtpStatusCode": "{{Activity.Field(SmtpStatusCode)}}",
									"SmtpMessage": "{{Activity.Field(SmtpMessage)}}"
									},
									"filter": "'{{Activity.Type}}'='Bounceback'",
									"dataRetentionDuration": "PT12H",
									"uri": "/activities/exports/76",
									"createdBy": "API.User",
									"createdAt": "2018-10-10T13:49:44.7566016Z",
									"updatedBy": "API.User",
									"updatedAt": "2018-10-10T13:49:44.7566016Z"
								}

You can now include user fields for EmailOpen, EmailClickthrough, and EmailSend activity export definitions. One use case this enhancement enables, is allowing including sender and user attributes on email activities exported via the Bulk API, so that the activity can be properly assigned to the correct user in CRM.

Discover user fields using the retrieve a list of user fields endpoint (GET /api/bulk/2.0/users/fields). This endpoint will be documented in a future release.

User fields can be added with the following statement: {{Activity.User.Field(<Field Name>)}}
See a list of user fields, by Field Name, that can be included
- UserId (Eloqua User ID)
- Signature Layout Fields
  Company (Company Display Name)
  CompanyURL (Company Website URL)
  JobTitle (Job Title)
  Phone (Business Phone)
  CellPhone (Mobile Phone)
  SenderDisplayName (Email Sender Display Name)
  ReplyToAddress (Email Reply-To Address)
  Department (Department)
  Fax (Fax Number)
  Address1 (First Address)
  Address2 (Second Address)
  City (City)
  State (State)
  Country (Country)
  Zip (Zip/Postal Code)
  EmailSenderAddress (Email Sender Address)
  PersonalURL (Personal Website URL)
  PersonalMessage (Personal Message)
- CRM User IDs
  CRMSfdcUserId (Salesforce User ID)
  CRMMSDUserId (MS Dynamics User ID)
  CRMOSCUserId (Oracle Sales Cloud User ID)
  CRMSODUserId (Siebel User ID)

Platform notices

App Developer Framework

There is now a Scheduling option available for app action steps on Campaign and Program Canvases. If a user sets certain days and hours under Scheduling, records that enter the step outside of the selected days and hours, will remain in an “Awaiting action” status until within the selected days and hours, at which time the Notification URL call will then be sent to the app.

See an example of how the Scheduling option will look

The ability to mark forms as internal so that form submissions are dropped, will be in Controlled Availability in Eloqua Release 18D and 19A. This feature includes the addition of a new property to Form API endpoints. You can request access to this feature by submitting a request to My Oracle Support.
Oracle Eloqua will be deprecating TLS 1.1 on January 18, 2019. Learn more

Documentation enhancements of note

We've added a new topic about Bulk API data types and how to retrieve more information about Bulk API data types. Learn more
We've added a new tutorial that explains how to use cURL to upload data to the Bulk API from a file on your local machine such as a .json or .csv file. Learn more

Release 18C

A list of developer-facing new features, significant recent changes, and platform notices for Oracle Eloqua release 18C.

New features

App Developer Framework

We've added a new endpoint to enable developers to retrieve feeder service instances. Retrieve up to 200 feeder service instances, searched by service instance GUID. For more information, see POST /api/cloud/1.0/feeders/instances.

Example

Retrieve 2 feeder service instances:

POST api/cloud/1.0/feeders/instances
									X-HTTP-Method-Override: SEARCH
								Content-Type: application/json

Request body:

{
									"ids": [
									"4de74ef1-bb2c-44d6-97ba-6acb1565bc58",
									"97e3f90e-6ef8-40a8-9554-588a72de440e"
									]
								}

Important: Remember to include the dashes for the service instance GUIDs. A 400 validation error will be returned if the dashes are omitted.

Request response:

{
									"items": [
									{
									"statement": "{{FeederInstance(4de74ef1bb2c44d697ba6acb1565bc58)}}",
									"dependentAssetType": "Campaign",
									"dependentAssetId": 6662,
									"requiresConfiguration": true,
									"uri": "/feeders/90289/instances/4de74ef1bb2c44d697ba6acb1565bc58",
									"createdBy": "API.User",
									"createdAt": "2018-06-01T17:57:00.1470000Z",
									"updatedBy": "API.User",
									"updatedAt": "2018-06-01T17:57:23.5130000Z"
									},
									{
									"statement": "{{FeederInstance(97e3f90e6ef840a89554588a72de440e)}}",
									"dependentAssetType": "Program",
									"dependentAssetId": 1385,
									"requiresConfiguration": true,
									"uri": "/feeders/90289/instances/97e3f90e6ef840a89554588a72de440e",
									"createdBy": "API.User",
									"createdAt": "2018-06-01T18:10:21.5700000Z",
									"updatedBy": "API.User",
									"updatedAt": "2018-06-01T18:10:36.8770000Z"
									}
									]
								}

Application API

A new property processingStepErrors has been added to the response to submitting a form (POST /api/REST/1.0/data/form/<formId>). This feature is available for Early Preview in 18C, and will be generally available with 18D. You can request access to this feature by submitting a request to My Oracle Support.

You can now retrieve a list of campaigns using the search parameter with the startAt parameter to filter campaigns by campaign activation date.

Bulk API

We've added new endpoints to enable developers to retrieve activity fields. Refer to the API documentation to learn how you can retrieve all activity fields, or retrieve an activity field by id.

You can now include campaign fields in activity export definitions. This enhancement enables developers to properly assign an activity to the correct campaign when data is exported from Eloqua to an external system.

Example: Create an activity export

Create a new activity export definition:

POST /api/bulk/2.0/activities/exports
								Content-Type: application/json

Request body:

{
									"filter": "'{{Activity.Type}}'='EmailOpen'",
									"name": "Bulk Activity Export - Email Open",
									"fields": {
									"ActivityId": "{{Activity.Id}}",
									"ActivityType": "{{Activity.Type}}",
									"ActivityDate": "{{Activity.CreatedAt}}",
									"ContactId": "{{Activity.Contact.Id}}",
									"IpAddress": "{{Activity.Field(IpAddress)}}",
									"VisitorId": "{{Activity.Visitor.Id}}",
									"VisitorExternalId": "{{Activity.Visitor.ExternalId}}",
									"EmailRecipientId": "{{Activity.Field(EmailRecipientId)}}",
									"AssetType": "{{Activity.Asset.Type}}",
									"AssetName": "{{Activity.Asset.Name}}",
									"AssetId": "{{Activity.Asset.Id}}",
									"SubjectLine": "{{Activity.Field(SubjectLine)}}",
									"EmailWebLink": "{{Activity.Field(EmailWebLink)}}",
									"CampaignId": "{{Activity.Campaign.Id}}",
									"CRMCampaignId": "{{Activity.Campaign.Field(CRMCampaignId)}}",
									"CampaignName": "{{Activity.Campaign.Field(CampaignName)}}",
									"ExternalId": "{{Activity.ExternalId}}",
									"DeploymentId": "{{Activity.Field(EmailDeploymentId)}}",
									"EmailSendType": "{{Activity.Field(EmailSendType)}}",
									"EmailAddress": "{{Activity.Field(EmailAddress)}}",
									"ContactIdExt": "{{Activity.Contact.Field(ContactIDExt)}}"
									}
								}

Request response:

{
									"name": "Bulk Activity Export - Email Open",
									"fields": {
									"ActivityId": "{{Activity.Id}}",
									"ActivityType": "{{Activity.Type}}",
									"ActivityDate": "{{Activity.CreatedAt}}",
									"ContactId": "{{Activity.Contact.Id}}",
									"IpAddress": "{{Activity.Field(IpAddress)}}",
									"VisitorId": "{{Activity.Visitor.Id}}",
									"VisitorExternalId": "{{Activity.Visitor.ExternalId}}",
									"EmailRecipientId": "{{Activity.Field(EmailRecipientId)}}",
									"AssetType": "{{Activity.Asset.Type}}",
									"AssetName": "{{Activity.Asset.Name}}",
									"AssetId": "{{Activity.Asset.Id}}",
									"SubjectLine": "{{Activity.Field(SubjectLine)}}",
									"EmailWebLink": "{{Activity.Field(EmailWebLink)}}",
									"CampaignId": "{{Activity.Campaign.Id}}",
									"CRMCampaignId": "{{Activity.Campaign.Field(CRMCampaignId)}}",
									"CampaignName": "{{Activity.Campaign.Field(CampaignName)}}",
									"ExternalId": "{{Activity.ExternalId}}",
									"DeploymentId": "{{Activity.Field(EmailDeploymentId)}}",
									"EmailSendType": "{{Activity.Field(EmailSendType)}}",
									"EmailAddress": "{{Activity.Field(EmailAddress)}}",
									"ContactIdExt": "{{Activity.Contact.Field(ContactIDExt)}}"
									},
									"filter": "'{{Activity.Type}}'='EmailOpen'",
									"dataRetentionDuration": "PT12H",
									"uri": "/activities/exports/66",
									"createdBy": "API.User",
									"createdAt": "2018-07-17T14:50:52.3183789Z",
									"updatedBy": "API.User",
									"updatedAt": "2018-07-17T14:50:52.3183789Z"
								}

Recent changes

The Campaign Response endpoints are now generally optional. These endpoints enable developers to access campaign responses, to support the specific use case of updating a campaign response status in CRM via an App on Program or Campaign Canvas. These endpoints can only be used by an App service instance selected in Response Rules setup, and cannot be accessed otherwise. Submit a request to My Oracle Support to start using this feature. You can learn more about Campaign Responses by reading the tutorial or referring to the API documentation.
Optimizations have been made to EmailOpen and EmailClickthrough Bulk API exports that include Activity Date in the filter.
The “Manage Contact Fields” Action Permission is now required to create, update, and delete Contacts via the Contact fields Application API endpoints. Learn more
The "Define External Assets and Activities" Action Permission is now required to create, update, or delete External Assets and External Asset Types using the Application API endpoints. Learn more
Access to Eloqua's Web Services Description Language (WSDL) is now available only by submitting a request to My Oracle Support.

Documentation enhancements of note

The tutorial on how to use the search URL parameter now includes information on best practices when using a wildcard character. Learn more

Platform notices

With the arrival of Eloqua release 18D (Nov 16 - 17, 2018), the resendLimit property introduced in 18A will be removed from the processingSteps type FormStepSendEmail for Application API Form endpoints.
With the arrival of Eloqua release 18D (Nov 16 - 17, 2018), the Create an external activity Application API endpoint will no longer create External Asset Types or External Activity Types if they do not exist. Learn more

Release 18B

A list of developer-facing new features, significant recent changes, and platform notices for Oracle Eloqua release 18B.

New features

Application API

You can now use the Programs API in REST 2.0 to create, update, retrieve, delete, activate, deactivate, and pause Programs. Learn more.

Bulk API

We've added opportunities endpoints that enable developers to import opportunities into Eloqua's opportunity object. Developers can then perform another import to link the opportunities with Eloqua contacts. For more information on these endpoints, see the API documentation or the tutorial.

Example: Create an opportunity import definition

Create an opportunity import definition:

POST /opportunities/imports
								Content-Type: application/json

Request body:

{
									"name": "Opportunity Import",
									"fields": {
									"OpportunityID": "{{Opportunity.Id}}",
									"OpportunityName": "{{Opportunity.Field(Name)}}",
									"AccountName": "{{Opportunity.Field(AccountName)}}",
									"CreatedDate": "{{Opportunity.CreatedAt}}",
									"Amount": "{{Opportunity.Field(Amount)}}",
									"CloseDate": "{{Opportunity.Field(CloseDate)}}",
									"Currency": "{{Opportunity.Field(Currency)}}",
									"ForecastToCloseDate": "{{Opportunity.Field(ForecastToCloseDate)}}",
									"Stage": "{{Opportunity.Field(Stage)}}",
									"Territory": "{{Opportunity.Field(Territory)}}"
									},
									"identifierFieldName": "OpportunityID",
									"isIdentifierFieldCaseSensitive": false
								}

Request response:

{
									"isIdentifierFieldCaseSensitive": false,
									"name": "Opportunity Import",
									"fields": {
									"OpportunityID": "{{Opportunity.Id}}",
									"OpportunityName": "{{Opportunity.Field(Name)}}",
									"AccountName": "{{Opportunity.Field(AccountName)}}",
									"CreatedDate": "{{Opportunity.CreatedAt}}",
									"Amount": "{{Opportunity.Field(Amount)}}",
									"CloseDate": "{{Opportunity.Field(CloseDate)}}",
									"Currency": "{{Opportunity.Field(Currency)}}",
									"ForecastToCloseDate": "{{Opportunity.Field(ForecastToCloseDate)}}",
									"Stage": "{{Opportunity.Field(Stage)}}",
									"Territory": "{{Opportunity.Field(Territory)}}"
									},
									"identifierFieldName": "OpportunityID",
									"isSyncTriggeredOnImport": false,
									"dataRetentionDuration": "P7D",
									"uri": "/opportunities/imports/24",
									"createdBy": "API.User",
									"createdAt": "2018-02-15T15:28:32.4730364Z",
									"updatedBy": "API.User",
									"updatedAt": "2018-02-15T15:28:32.4730364Z"
								}

Example: Create a new opportunity contact linkage import definition

Create a new opportunity contact linkage import definition:

POST /opportunities/contacts/imports
								Content-Type: application/json

Request body:

{
									"name": "Opportunity Contact Linkage Import",
									"fields": {
									"EmailAddress": "{{Opportunity.Contact.Field(C_EmailAddress)}}",
									"OpportunityID": "{{Opportunity.Id}}"
									},
									"linkOpportunitiesCaseSensitiveMatchField": false,
									"linkOpportunitiesCaseSensitiveSourceField": false,
									"linkOpportunitiesEntityType": "Contact",
									"linkOpportunitiesMatchFieldName": "OpportunityID",
									"linkOpportunitiesMultipleSourceMatches": true,
									"linkOpportunitiesSourceField": "EmailAddress"
								}

Request response:

{
									"linkOpportunitiesMatchFieldName": "OpportunityID",
									"linkOpportunitiesSourceField": "EmailAddress",
									"linkOpportunitiesEntityType": "Contact",
									"linkOpportunitiesCaseSensitiveSourceField": false,
									"linkOpportunitiesCaseSensitiveMatchField": false,
									"linkOpportunitiesMultipleSourceMatches": true,
									"name": "Opportunity Contact Linkage Import",
									"fields": {
									"EmailAddress": "{{Opportunity.Contact.Field(C_EmailAddress)}}",
									"OpportunityID": "{{Opportunity.Id}}"
									},
									"identifierFieldName": "OpportunityID",
									"isSyncTriggeredOnImport": false,
									"dataRetentionDuration": "P7D",
									"uri": "/opportunities/contacts/imports/23",
									"createdBy": "API.User",
									"createdAt": "2018-02-15T15:03:43.3345307Z",
									"updatedBy": "API.User",
									"updatedAt": "2018-02-15T15:03:43.3345307Z"
								}

We've added a new parameter, nullIdentifierFieldName, that enables you to null the identifierFieldName when performing an account or contact import.

Recent changes

Prior to release 18B, it was possible for email sends to fail if an email was sent to deleted contacts. As of release 18B when emails are sent via any channel in Eloqua and one or more of the target contacts are in a deleted state, emails sent to that recipient will fail and a log entry is saved indicating why the email send failed.
Resolved an issue where retrieving a list of accounts in REST 1.0 wasn't returning values for custom account fields.
Resolved an issue where it was possible to update completed campaigns. Campaigns that are completed can no longer be updated.
As announced in Code It, the recordCount property has been removed. Learn more

Documentation enhancements of note

We've added a new tutorial to walkthrough how to use the search URL parameter for Eloqua's Application API. This tutorial contains usage details about the parameter and various examples about how the parameter can be used. Learn more
Added a new tutorial to walkthrough how to export all assets in an Eloqua database using the Application API. Learn more
Added viewId to the URL parameter list. Use the viewId parameter to specify a contact or account view to filter data according to that view. Learn more
Added an example that explains how to create a campaign with a custom end date. Learn more

Release 18A

A list of developer-facing new features, significant recent changes, and platform notices for Oracle Eloqua release 18A.

New features

Application API

We've added a new property, resendLimit, to the Application API Form endpoints when there is a FormStepSendEmail within processingSteps. This property controls the amount of times a form will attempt to resend an email. Learn more

Recent changes

Application API

Resolved an issue with the Retrieve visitor data Application API endpoint where V_TimeZone was returned inversed. In example, if the offset was UTC+5, it returned UTC-5.

Resolved an issue in REST 1.0 where creating or updating an account that contained custom account fields would result in the account being created or updated, but without the custom account fields.

Example

Creating an account with custom account fields prior to release 18A resulted in the custom field values being ignored and not set:

Request

POST /api/rest/1.0/data/account

Request body

{
									"name": "Account with custom account fields",
									"address2": "123 Redwood Shores",
									"fieldValues": [
									{
									"type": "FieldValue",
									"id": "100187",
									"value": "1"
									},
									{
									"type": "FieldValue",
									"id": "100193",
									"value": "1.5000"
									},
									{
									"type": "FieldValue",
									"id": "100212",
									"value": "123.1230"
									}
									]
								}

Response body

{
									"type": "Account",
									"id": "22",
									"createdAt": "1517415972",
									"depth": "complete",
									"description": "",
									"name": "Account with custom account fields",
									"updatedAt": "1517415972",
									"address1": "",
									"address2": "123 Redwood Shores",
									"address3": "",
									"businessPhone": "",
									"city": "",
									"country": "",
									"fieldValues": [],
									"postalCode": "",
									"province": ""
								}

Performing the same request in release 18A will now successfully create the account with the custom account fields.

Response body

{
									"type": "Account",
									"id": "22",
									"createdAt": "1517415972",
									"depth": "complete",
									"description": "",
									"name": "Account with custom account fields",
									"updatedAt": "1517415972",
									"address1": "",
									"address2": "123 Redwood Shores",
									"address3": "",
									"businessPhone": "",
									"city": "",
									"country": "",
									"fieldValues": [
									{
									"type": "FieldValue",
									"id": "100187",
									"value": "1"
									},
									{
									"type": "FieldValue",
									"id": "100193",
									"value": "1.5000"
									},
									{
									"type": "FieldValue",
									"id": "100212",
									"value": "123.1230"
									}
									],
									"postalCode": "",
									"province": ""
								}

Bulk API

Resolved an issue where Bulk API activity exports including contact fields were failing when Label-Based Access Control was enabled.
Improved validation for Bulk API activity exports to return a validation error if including contact fields without an Activity root. There was validation missing which allowed field statements to be used in activity exports such as:

{{Contact.Field(<contact_field_name>)}}

This is incorrect, and will now throw a validation error. The correct syntax for using a contact field statement in an activity export is:

{{Activity.Contact.Field(<contact_field_name>)}}

Platform notices

Emails created in the New Design Editor, Generally Available in Release 18A, will only be accessible via the Email 2.0 endpoints.

Release 493

A list of developer-facing new features, significant recent changes, and platform notices for Oracle Eloqua release 493.

New features

Bulk API

We've added new endpoints to enable developers to access campaign responses, to support the specific use case of updating a campaign response status in CRM via an App on Program or Campaign Canvas. These endpoints can only be used by an App service instance selected in Response Rules setup, and cannot be accessed otherwise. This feature is currently in Controlled Availability. Learn more

Application API

You can now use the Emails API in REST 2.0 to create, update, retrieve, and delete emails. Learn more.

Recent changes

Application API

Resolved an issue in REST 2.0 where retrieving custom object data would return incorrect date values. For example, a custom object field value saved as 2017-03-04 should return epoch time of March 4, 2017, but instead returned epoch time of April 3, 2017 when the output format is set to dd/mm/yyyy.
Resolved two issues in REST 2.0 where creating a custom object instance would return an incorrect value for name, and not display all fields.
Resolved two issues in REST 2.0 where retrieving a custom object instance did not return the depth or isMapped properties.
Resolved an issue in REST 2.0 where retrieving custom object data and filtering by custom object field would result in an error if the field name started with a number.
Resolved an instance where it was possible for an email deployment to fail if a single email deployment was being sent to multiple contacts with the same email address. This issue only affected instances where contacts can exist without an email address and duplicate email addresses are enabled.

Bulk API

Prior to release 493, email activities exported via the Bulk API would include the current subject line of the email. With 493, email activities exported via the Bulk API will include the subject line at the time of email send.
When viewing dependencies for contact and account fields in the Fields and Views area of Eloqua, Bulk API Import and Export dependencies are now displayed within the dependency checker.

Release 492

A list of developer-facing new features, significant recent changes, and platform notices for Oracle Eloqua release 492.

New features

Bulk API

The /api/bulk/2.0/syncs/{id}/logs endpoint has been improved to more efficiently handle fields included in data upload that are not included in an import definition. Previously, the sync logs would display a separate message per field not included in the import definition, per record it's included in. With this update, a field is only mentioned once in sync log messaging even if the field is included multiple times.

Example: Retrieving a sync's logs prior to Release 492

Contact import definition:

{
								"name": "Example Import",
								"fields": {
								"EmailAddress": "{{Contact.Field(C_EmailAddress)}}"
								},
								"identifierFieldName": "EmailAddress",
								"syncActions": [],
								"isSyncTriggeredOnImport": false,
								"dataRetentionDuration": "P7D",
								"isUpdatingMultipleMatchedRecords": false,
								"uri": "/contacts/imports/47",
								"createdBy": "API.User",
								"createdAt": "2017-02-14T23:43:20.4570000Z",
								"updatedBy": "API.User",
								"updatedAt": "2017-02-14T23:43:20.4570000Z"
							}

Uploaded data:

[
								{
								"EmailAddress": "fieldnotindef1@test.elq",
								"notindeffield1": "1"
								},
								{
								"EmailAddress": "fieldnotindef2@test.elq",
								"notindeffield1": "1",
								"notindeffield2": "2"
								},
								{
								"EmailAddress": "fieldnotindef3@test.elq",
								"notindeffield1": "1",
								"notindeffield2": "2",
								"notindeffield3": "3"
								},
								{
								"EmailAddress": "fieldnotindef4@test.elq",
								"notindeffield1": "1",
								"notindeffield2": "2",
								"notindeffield3": "3",
								"notindeffield4": "4"
								},
								{
								"EmailAddress": "fieldnotindef5@test.elq",
								"notindeffield1": "1",
								"notindeffield2": "2",
								"notindeffield3": "3",
								"notindeffield4": "4",
								"notindeffield5": "5"
								}
							]

Sync logs:

{
								"items": [
								{
								"syncUri": "/syncs/178",
								"count": 0,
								"severity": "warning",
								"statusCode": "ELQ-00111",
								"message": "Field (notindeffield1) is not part of import definition, and will be ignored.",
								"createdAt": "2017-02-16T22:39:48.5230000Z"
								},
								{
								"syncUri": "/syncs/178",
								"count": 0,
								"severity": "warning",
								"statusCode": "ELQ-00111",
								"message": "Field (notindeffield1) is not part of import definition, and will be ignored.",
								"createdAt": "2017-02-16T22:39:48.5230000Z"
								},
								{
								"syncUri": "/syncs/178",
								"count": 0,
								"severity": "warning",
								"statusCode": "ELQ-00111",
								"message": "Field (notindeffield2) is not part of import definition, and will be ignored.",
								"createdAt": "2017-02-16T22:39:48.5230000Z"
								},
								{
								"syncUri": "/syncs/178",
								"count": 0,
								"severity": "warning",
								"statusCode": "ELQ-00111",
								"message": "Field (notindeffield1) is not part of import definition, and will be ignored.",
								"createdAt": "2017-02-16T22:39:48.5230000Z"
								},
								{
								"syncUri": "/syncs/178",
								"count": 0,
								"severity": "warning",
								"statusCode": "ELQ-00111",
								"message": "Field (notindeffield2) is not part of import definition, and will be ignored.",
								"createdAt": "2017-02-16T22:39:48.5230000Z"
								},
								{
								"syncUri": "/syncs/178",
								"count": 0,
								"severity": "warning",
								"statusCode": "ELQ-00111",
								"message": "Field (notindeffield3) is not part of import definition, and will be ignored.",
								"createdAt": "2017-02-16T22:39:48.5230000Z"
								},
								{
								"syncUri": "/syncs/178",
								"count": 0,
								"severity": "warning",
								"statusCode": "ELQ-00111",
								"message": "Field (notindeffield1) is not part of import definition, and will be ignored.",
								"createdAt": "2017-02-16T22:39:48.5230000Z"
								},
								{
								"syncUri": "/syncs/178",
								"count": 0,
								"severity": "warning",
								"statusCode": "ELQ-00111",
								"message": "Field (notindeffield2) is not part of import definition, and will be ignored.",
								"createdAt": "2017-02-16T22:39:48.5230000Z"
								},
								{
								"syncUri": "/syncs/178",
								"count": 0,
								"severity": "warning",
								"statusCode": "ELQ-00111",
								"message": "Field (notindeffield3) is not part of import definition, and will be ignored.",
								"createdAt": "2017-02-16T22:39:48.5230000Z"
								},
								{
								"syncUri": "/syncs/178",
								"count": 0,
								"severity": "warning",
								"statusCode": "ELQ-00111",
								"message": "Field (notindeffield4) is not part of import definition, and will be ignored.",
								"createdAt": "2017-02-16T22:39:48.5230000Z"
								},
								{
								"syncUri": "/syncs/178",
								"count": 0,
								"severity": "warning",
								"statusCode": "ELQ-00111",
								"message": "Field (notindeffield1) is not part of import definition, and will be ignored.",
								"createdAt": "2017-02-16T22:39:48.5230000Z"
								},
								{
								"syncUri": "/syncs/178",
								"count": 0,
								"severity": "warning",
								"statusCode": "ELQ-00111",
								"message": "Field (notindeffield2) is not part of import definition, and will be ignored.",
								"createdAt": "2017-02-16T22:39:48.5230000Z"
								},
								{
								"syncUri": "/syncs/178",
								"count": 0,
								"severity": "warning",
								"statusCode": "ELQ-00111",
								"message": "Field (notindeffield3) is not part of import definition, and will be ignored.",
								"createdAt": "2017-02-16T22:39:48.5230000Z"
								},
								{
								"syncUri": "/syncs/178",
								"count": 0,
								"severity": "warning",
								"statusCode": "ELQ-00111",
								"message": "Field (notindeffield4) is not part of import definition, and will be ignored.",
								"createdAt": "2017-02-16T22:39:48.5230000Z"
								},
								{
								"syncUri": "/syncs/178",
								"count": 0,
								"severity": "warning",
								"statusCode": "ELQ-00111",
								"message": "Field (notindeffield5) is not part of import definition, and will be ignored.",
								"createdAt": "2017-02-16T22:39:48.5230000Z"
								},
								{
								"syncUri": "/syncs/178",
								"count": 5,
								"severity": "information",
								"statusCode": "ELQ-00130",
								"message": "Total records staged for import.",
								"createdAt": "2017-02-16T22:39:48.7430000Z"
								},
								{
								"syncUri": "/syncs/178",
								"count": 0,
								"severity": "information",
								"statusCode": "ELQ-00137",
								"message": "Ready for data import processing.",
								"createdAt": "2017-02-16T22:39:48.7600000Z"
								},
								{
								"syncUri": "/syncs/178",
								"count": 0,
								"severity": "information",
								"statusCode": "ELQ-00101",
								"message": "Sync processed for sync , resulting in Warning status.",
								"createdAt": "2017-02-16T22:39:50.1500000Z"
								},
								{
								"syncUri": "/syncs/178",
								"count": 5,
								"severity": "information",
								"statusCode": "ELQ-00001",
								"message": "Total records processed.",
								"createdAt": "2017-02-16T22:39:48.7200000Z"
								},
								{
								"syncUri": "/syncs/178",
								"count": 5,
								"severity": "information",
								"statusCode": "ELQ-00004",
								"message": "Contacts created.",
								"createdAt": "2017-02-16T22:39:49.5430000Z"
								},
								{
								"syncUri": "/syncs/178",
								"count": 0,
								"severity": "information",
								"statusCode": "ELQ-00022",
								"message": "Contacts updated.",
								"createdAt": "2017-02-16T22:39:49.5430000Z"
								}
								],
								"totalResults": 21,
								"limit": 1000,
								"offset": 0,
								"count": 21,
								"hasMore": false
							}

Example: Retrieving a sync's logs in Release 492

Contact import definition:

{
								"name": "test",
								"fields": {
								"EmailAddress": "{{Contact.Field(C_EmailAddress)}}"
								},
								"identifierFieldName": "EmailAddress",
								"syncActions": [],
								"isSyncTriggeredOnImport": false,
								"dataRetentionDuration": "P7D",
								"isUpdatingMultipleMatchedRecords": false,
								"uri": "/contacts/imports/47",
								"createdBy": "API.User",
								"createdAt": "2017-02-14T23:43:20.4570000Z",
								"updatedBy": "API.User",
								"updatedAt": "2017-02-14T23:43:20.4570000Z"
							}

Uploaded data:

[
								{
								"EmailAddress": "fieldnotindef1@test.elq",
								"notindeffield1": "1"
								},
								{
								"EmailAddress": "fieldnotindef2@test.elq",
								"notindeffield1": "1",
								"notindeffield2": "2"
								},
								{
								"EmailAddress": "fieldnotindef3@test.elq",
								"notindeffield1": "1",
								"notindeffield2": "2",
								"notindeffield3": "3"
								},
								{
								"EmailAddress": "fieldnotindef4@test.elq",
								"notindeffield1": "1",
								"notindeffield2": "2",
								"notindeffield3": "3",
								"notindeffield4": "4"
								},
								{
								"EmailAddress": "fieldnotindef5@test.elq",
								"notindeffield1": "1",
								"notindeffield2": "2",
								"notindeffield3": "3",
								"notindeffield4": "4",
								"notindeffield5": "5"
								}
							]

Sync logs:

{
								"items": [
								{
								"syncUri": "/syncs/178",
								"count": 0,
								"severity": "warning",
								"statusCode": "ELQ-00111",
								"message": "Field (notindeffield1) is not part of import definition, and will be ignored.",
								"createdAt": "2017-02-16T22:39:48.5230000Z"
								},
								{
								"syncUri": "/syncs/178",
								"count": 0,
								"severity": "warning",
								"statusCode": "ELQ-00111",
								"message": "Field (notindeffield2) is not part of import definition, and will be ignored.",
								"createdAt": "2017-02-16T22:39:48.5230000Z"
								},
								{
								"syncUri": "/syncs/178",
								"count": 0,
								"severity": "warning",
								"statusCode": "ELQ-00111",
								"message": "Field (notindeffield3) is not part of import definition, and will be ignored.",
								"createdAt": "2017-02-16T22:39:48.5230000Z"
								},
								{
								"syncUri": "/syncs/178",
								"count": 0,
								"severity": "warning",
								"statusCode": "ELQ-00111",
								"message": "Field (notindeffield4) is not part of import definition, and will be ignored.",
								"createdAt": "2017-02-16T22:39:48.5230000Z"
								},
								{
								"syncUri": "/syncs/178",
								"count": 0,
								"severity": "warning",
								"statusCode": "ELQ-00111",
								"message": "Field (notindeffield5) is not part of import definition, and will be ignored.",
								"createdAt": "2017-02-16T22:39:48.5230000Z"
								},
								{
								"syncUri": "/syncs/178",
								"count": 5,
								"severity": "information",
								"statusCode": "ELQ-00130",
								"message": "Total records staged for import.",
								"createdAt": "2017-02-16T22:39:48.7430000Z"
								},
								{
								"syncUri": "/syncs/178",
								"count": 0,
								"severity": "information",
								"statusCode": "ELQ-00137",
								"message": "Ready for data import processing.",
								"createdAt": "2017-02-16T22:39:48.7600000Z"
								},
								{
								"syncUri": "/syncs/178",
								"count": 0,
								"severity": "information",
								"statusCode": "ELQ-00101",
								"message": "Sync processed for sync , resulting in Warning status.",
								"createdAt": "2017-02-16T22:39:50.1500000Z"
								},
								{
								"syncUri": "/syncs/178",
								"count": 5,
								"severity": "information",
								"statusCode": "ELQ-00001",
								"message": "Total records processed.",
								"createdAt": "2017-02-16T22:39:48.7200000Z"
								},
								{
								"syncUri": "/syncs/178",
								"count": 5,
								"severity": "information",
								"statusCode": "ELQ-00004",
								"message": "Contacts created.",
								"createdAt": "2017-02-16T22:39:49.5430000Z"
								},
								{
								"syncUri": "/syncs/178",
								"count": 0,
								"severity": "information",
								"statusCode": "ELQ-00022",
								"message": "Contacts updated.",
								"createdAt": "2017-02-16T22:39:49.5430000Z"
								}
								],
								"totalResults": 11,
								"limit": 1000,
								"offset": 0,
								"count": 11,
								"hasMore": false
							}

Recent changes

Application API

Prior to 492, it was possible to update the runAsUserId property while a campaign was Active using the Update a campaign endpoint. This could have resulted in users not being able to deactivate campaigns. With 492 the runAsUserId property will no longer be able to be changed while a campaign is Active.

Release 491

A list of developer-facing new features, significant recent changes, and platform notices for Oracle Eloqua release 491.

New features

Application API

We have modified the endpoints used to retrieve Events, so that partial depth will return all properties except for sessions, sessionFieldValues, emailAddressFieldId, eventGroupByFieldId, and uniqueCodeFieldId. Currently, partial depth returns all properties. Learn more
You can now use the Contact Segments API in REST 2.0 to create, update, retrieve, delete, and copy contact segments. Learn more

Bulk API

Added the ability to include up to 10 contact fields in an activity export definition. Note that the addition of contact fields to activity exports will add to export time. If more than 10 contact fields are included, Eloqua will respond with a 400 validation error. The syntax for a contact field statement in a Bulk API activity export definition is:

{{Activity.Contact.Field(<contact_field_name>)}}

Example

Create an activity export definition using the contact field ContactIdExt to retrieve a contact’s Eloqua ID:

Request

POST /api/bulk/2.0/activities/exports

Request body

{
								"filter": "'{{Activity.Type}}'='EmailOpen'",
								"name": "Bulk Activity Export - Email Open",
								"fields": {
								"ActivityId": "{{Activity.Id}}",
								"ActivityType": "{{Activity.Type}}",
								"ActivityDate": "{{Activity.CreatedAt}}",
								"ContactId": "{{Activity.Contact.Id}}",
								"IpAddress": "{{Activity.Field(IpAddress)}}",
								"VisitorId": "{{Activity.Visitor.Id}}",
								"VisitorExternalId": "{{Activity.Visitor.ExternalId}}",
								"EmailRecipientId": "{{Activity.Field(EmailRecipientId)}}",
								"AssetType": "{{Activity.Asset.Type}}",
								"AssetName": "{{Activity.Asset.Name}}",
								"AssetId": "{{Activity.Asset.Id}}",
								"SubjectLine": "{{Activity.Field(SubjectLine)}}",
								"EmailWebLink": "{{Activity.Field(EmailWebLink)}}",
								"CampaignId": "{{Activity.Campaign.Id}}",
								"ExternalId": "{{Activity.ExternalId}}",
								"DeploymentId": "{{Activity.Field(EmailDeploymentId)}}",
								"EmailSendType": "{{Activity.Field(EmailSendType)}}",
								"EmailAddress": "{{Activity.Field(EmailAddress)}}",
								"ContactIdExt": "{{Activity.Contact.Field(ContactIDExt)}}"
								}
							}

Response body

{
								"name": "Bulk Activity Export - Email Open",
								"fields": {
								"ActivityId": "{{Activity.Id}}",
								"ActivityType": "{{Activity.Type}}",
								"ActivityDate": "{{Activity.CreatedAt}}",
								"ContactId": "{{Activity.Contact.Id}}",
								"IpAddress": "{{Activity.Field(IpAddress)}}",
								"VisitorId": "{{Activity.Visitor.Id}}",
								"VisitorExternalId": "{{Activity.Visitor.ExternalId}}",
								"EmailRecipientId": "{{Activity.Field(EmailRecipientId)}}",
								"AssetType": "{{Activity.Asset.Type}}",
								"AssetName": "{{Activity.Asset.Name}}",
								"AssetId": "{{Activity.Asset.Id}}",
								"SubjectLine": "{{Activity.Field(SubjectLine)}}",
								"EmailWebLink": "{{Activity.Field(EmailWebLink)}}",
								"CampaignId": "{{Activity.Campaign.Id}}",
								"ExternalId": "{{Activity.ExternalId}}",
								"DeploymentId": "{{Activity.Field(EmailDeploymentId)}}",
								"EmailSendType": "{{Activity.Field(EmailSendType)}}",
								"EmailAddress": "{{Activity.Field(EmailAddress)}}",
								"ContactIdExt": "{{Activity.Contact.Field(ContactIDExt)}}"
								},
								"filter": "'{{Activity.Type}}'='EmailOpen'",
								"dataRetentionDuration": "PT12H",
								"uri": "/activities/exports/1560",
								"createdBy": "API.User",
								"createdAt": "2017-08-09T16:22:09.0434041Z",
								"updatedBy": "API.User",
								"updatedAt": "2017-08-09T16:22:09.0434041Z"
							}

You can now include the following fields when creating a Bounceback activity export definition:

EmailRecipientId
EmailDeploymentId
SmtpErrorCode
SmtpStatusCode
SmtpMessage

This enhancement enables developers to tie a hard Bounceback to an email send, and provides further details on the Bounceback. For more information on these fields, see Activity Fields.

Example

Create a Bounceback activity export definition:

Request

POST /api/bulk/2.0/activities/exports

Request body

{
								"filter": "'{{Activity.Type}}'='Bounceback'",
								"name": "Bulk Activity Export - Bounceback",
								"fields": {
								"ActivityId": "{{Activity.Id}}",
								"ActivityType": "{{Activity.Type}}",
								"ActivityDate": "{{Activity.CreatedAt}}",
								"EmailAddress": "{{Activity.Field(EmailAddress)}}",
								"AssetType": "{{Activity.Asset.Type}}",
								"AssetName": "{{Activity.Asset.Name}}",
								"AssetId": "{{Activity.Asset.Id}}",
								"CampaignId": "{{Activity.Campaign.Id}}",
								"ExternalId": "{{Activity.ExternalId}}",
								"EmailRecipientId": "{{Activity.Field(EmailRecipientId)}}",
								"DeploymentId": "{{Activity.Field(EmailDeploymentId)}}",
								"SmtpErrorCode": "{{Activity.Field(SmtpErrorCode)}}",
								"SmtpStatusCode": "{{Activity.Field(SmtpStatusCode)}}",
								"SmtpMessage": "{{Activity.Field(SmtpMessage)}}"
								}
							}

Response body

{
								"name": "Bulk Activity Export - Bounceback",
								"fields": {
								"ActivityId": "{{Activity.Id}}",
								"ActivityType": "{{Activity.Type}}",
								"ActivityDate": "{{Activity.CreatedAt}}",
								"EmailAddress": "{{Activity.Field(EmailAddress)}}",
								"AssetType": "{{Activity.Asset.Type}}",
								"AssetName": "{{Activity.Asset.Name}}",
								"AssetId": "{{Activity.Asset.Id}}",
								"CampaignId": "{{Activity.Campaign.Id}}",
								"ExternalId": "{{Activity.ExternalId}}",
								"EmailRecipientId": "{{Activity.Field(EmailRecipientId)}}",
								"DeploymentId": "{{Activity.Field(EmailDeploymentId)}}",
								"SmtpErrorCode": "{{Activity.Field(SmtpErrorCode)}}",
								"SmtpStatusCode": "{{Activity.Field(SmtpStatusCode)}}",
								"SmtpMessage": "{{Activity.Field(SmtpMessage)}}"
								},
								"filter": "'{{Activity.Type}}'='Bounceback'",
								"dataRetentionDuration": "PT12H",
								"uri": "/activities/exports/51",
								"createdBy": "API.User",
								"createdAt": "2017-08-18T17:39:41.3427356Z",
								"updatedBy": "API.User",
								"updatedAt": "2017-08-18T17:39:41.3427356Z"
							}

Retrieve the data:

GET /api/bulk/2.0/syncs/26697/data?limit=1

Response body:

{
								"totalResults": 177417,
								"limit": 1,
								"offset": 0,
								"count": 1,
								"hasMore": true,
								"items": [
								{
								"ActivityId": "22838",
								"ActivityType": "Bounceback",
								"ActivityDate": "2015-08-21 02:47:07.000",
								"EmailAddress": "john.doe@gmail.com",
								"AssetType": "Email",
								"AssetName": "Modern Marketing Experience 2018",
								"AssetId": "2842",
								"CampaignId": "1482",
								"ExternalId": "BBM1P3000000022838",
								"EmailRecipientId": "08daac6a-5de0-47ce-b99e-b73f05c97ff9",
								"DeploymentId": "4197",
								"SmtpErrorCode": "5.1.1",
								"SmtpStatusCode": "550",
								"SmtpMessage": "The email account that you tried to reach does not exist. Please try\\r\\n550-5.1.1 double-checking the recipient's email address for typos or\\r\\n550-5.1.1 unnecessary spaces. Learn more at\\r\\n550 5.1.1  https://support.google.com/mail/answer/6596"
							},

Recent changes

Bulk API

Resolved an instance where creating a Feeder sync action definition for custom objects was causing an error.
Modified the behavior of the ExternalId field on custom objects. The ExternalId field can now be used as the identifierFieldName on bulk imports even if there is a unique code field set on the destination custom object.

Release 490

A list of developer-facing new features, significant recent changes, and platform notices for Oracle Eloqua release 490.

New features

Application API

When retrieving a list of custom object data in REST 2.0, you can now filter by uniqueCode as a search query parameter to filter results. Each custom object data entity contains a unique code that can be used in a filter. Learn more

Recent changes

Application API

Resolved an issue where retrieving a list of custom object data in REST 2.0 when ordering by updatedAt would result in an error. You can now send this request ordering results using updatedAt in REST 2.0.
Example
Retrieve a list of custom object data and order results by updated date:

Request
```
GET /api/rest/2.0/data/customObject/25/instances?orderby=updatedAt
```
The custom object data API in REST 1.0 and 2.0 will no longer result in an error when using name in the search query parameter to filter results.
Examples
In REST 1.0, retrieve a list of custom object data and filter results by name:

Request
```
GET /api/rest/1.0/data/customObject/25?search=name=john.doe@oracle.com
```
In REST 2.0, retrieve a list of custom object data and filter results by name:

Request
```
GET /api/rest/2.0/data/customObject/25instances?search=name=john.doe@oracle.com
```

Release 489

A list of developer-facing new features, significant recent changes, and platform notices for Oracle Eloqua release 489.

New features

Bulk API

Syncs

We've created a new endpoint to allow developers to delete sync data from the staging area using sync id:

DELETE /api/bulk/2.0/syncs/{id}/data. Learn more

This new endpoint enables developers to delete sync data from the staging area, without having to use the various definitions data endpoints available. Prior to Release 489, to delete sync data, developers needed to use the specific definition data endpoint (/<entity>/exports/{id}/data). This method removes data for any syncs using the definition.

The new DELETE /api/bulk/2.0/syncs/{id}/data endpoint provides developers another way to delete sync data using sync id, without removing data for the same definition within a different sync.
Examples: Delete sync data
Delete sync data using sync id

Delete the data for the sync with ID = 40 (use this endpoint to delete sync data tied to a specific sync):

Request
```
DELETE /api/bulk/2.0/syncs/40/data
```
Response status (For DELETE requests, no body is returned):

204 No Content

Delete sync data using definition data endpoint

Delete the data for the contact export definition with ID = 50 (use this endpoint to delete all sync data tied to a definition):

Request
```
DELETE /api/bulk/2.0/contacts/exports/50/data
```
Response status (For DELETE requests, no body is returned):

204 No Content

Recent changes

Application API

When retrieving campaigns, we've modified the properties returned when depth is set to partial. Prior to Release 489, partial depth would return all properties. Partial depth will now return all properties except for:
- elements
- isReadOnly
- isMemberAllowedReEntry
Learn more
The form data API api/REST/1.0/data/form will no longer create a new visitor or new thread when no field with the HTML name elqCustomerGUID is passed to the REST API. As no thread is being created, form submits will not create a new website visit activity record.

Release 488

A list of developer-facing new features, significant recent changes, and platform notices for Oracle Eloqua release 488.

New features

Application API

Events

You can now use the events API endpoints to create, update, retrieve, and delete events. This functionality was previously only supported via the SOAP API, which has been deprecated. These new endpoints provide access to event fields that were not available via the SOAP API. Learn more

Example: Create an event

Create an event:

POST api/REST/2.0/assets/eventRegistration
							Content-Type: application/json

Request body:

{
								"name": "Modern Marketing Experience",
								"description": "Modern Marketing Experience brings together Modern Marketers from around the globe",
								"emailAddressFieldId": "-2",
								"fields": [
								{
								"type": "CustomObjectField",
								"id": "-2",
								"name": "Email",
								"dataType": "text",
								"displayType": "text"
								},
								{
								"type": "CustomObjectField",
								"name": "First Name",
								"dataType": "text",
								"displayType": "text"
								},
								{
								"type": "CustomObjectField",
								"name": "Industry",
								"dataType": "text",
								"displayType": "singleSelect",
								"optionListId": "9"
								},
								{
								"type": "CustomObjectField",
								"name": "Markie Submitted",
								"checkedValue": "Yes",
								"dataType": "text",
								"defaultValue": "No",
								"displayType": "checkbox",
								"uncheckedValue": "No"
								},
								{
								"type": "CustomObjectField",
								"name": "Birthday",
								"dataType": "date",
								"displayType": "text"
								},
								{
								"type": "CustomObjectField",
								"name": "Years Using Eloqua",
								"dataType": "number",
								"displayType": "text"
								},
								{
								"type": "CustomObjectField",
								"name": "MME Location",
								"dataType": "text",
								"defaultValue": "North America",
								"displayType": "singleSelect",
								"optionListId": "108"
								}
								],
								"sessionFields": [
								{
								"type": "EventSessionField",
								"name": "Date",
								"dataType": "date",
								"outputFormat": {
								"type": "FieldOutputFormat",
								"id": "19"
								}
								},
								{
								"type": "EventSessionField",
								"name": "Location",
								"dataType": "text"
								}
								],
								"sessions": [
								{
								"type": "EventSession",
								"name": "North America"
								},
								{
								"type": "EventSession",
								"name": "Europe"
								}
								],
								"uniqueCodeFieldId": "-2"
							}

Request response:

{
								"type": "EventRegistration",
								"id": "1260",
								"createdAt": "1493156690",
								"createdBy": "71",
								"depth": "complete",
								"description": "Modern Marketing Experience brings together Modern Marketers from around the globe",
								"folderId": "81",
								"name": "Modern Marketing Experience",
								"updatedAt": "1493156690",
								"updatedBy": "71",
								"emailAddressFieldId": "3958",
								"fields": [
								{
								"type": "CustomObjectField",
								"id": "3958",
								"initialId": "-2",
								"depth": "complete",
								"name": "Email",
								"dataType": "text",
								"displayType": "text",
								"internalName": "Email1"
								},
								{
								"type": "CustomObjectField",
								"id": "3959",
								"depth": "complete",
								"name": "First Name",
								"dataType": "text",
								"displayType": "text",
								"internalName": "First_Name1"
								},
								{
								"type": "CustomObjectField",
								"id": "3960",
								"depth": "complete",
								"name": "Industry",
								"dataType": "text",
								"displayType": "singleSelect",
								"internalName": "Industry1",
								"optionListId": "9"
								},
								{
								"type": "CustomObjectField",
								"id": "3961",
								"depth": "complete",
								"name": "Markie Submitted",
								"checkedValue": "Yes",
								"dataType": "text",
								"defaultValue": "No",
								"displayType": "checkbox",
								"internalName": "Markie_Submitted1",
								"uncheckedValue": "No"
								},
								{
								"type": "CustomObjectField",
								"id": "3962",
								"depth": "complete",
								"name": "Birthday",
								"dataType": "date",
								"displayType": "text",
								"internalName": "Birthday1"
								},
								{
								"type": "CustomObjectField",
								"id": "3963",
								"depth": "complete",
								"name": "Years Using Eloqua",
								"dataType": "number",
								"displayType": "text",
								"internalName": "Years_Using_Eloqua1"
								},
								{
								"type": "CustomObjectField",
								"id": "3964",
								"depth": "complete",
								"name": "MME Location",
								"dataType": "text",
								"defaultValue": "North America",
								"displayType": "singleSelect",
								"internalName": "MME_Location1",
								"optionListId": "108"
								}
								],
								"recordCount": 0,
								"sessionFields": [
								{
								"type": "EventSessionField",
								"id": "535",
								"name": "Date",
								"dataType": "date",
								"outputFormat": {
								"type": "FieldOutputFormat",
								"id": "19",
								"dataType": "date",
								"format": "dddd MMMM d, yyyy"
								}
								},
								{
								"type": "EventSessionField",
								"id": "536",
								"name": "Location",
								"dataType": "text"
								}
								],
								"sessions": [
								{
								"type": "EventSession",
								"id": "51",
								"name": "North America"
								},
								{
								"type": "EventSession",
								"id": "52",
								"name": "Europe"
								}
								],
								"uniqueCodeFieldId": "3958"
							}

Event Registrants

You can now use the Event registrants API endpoints to create, update, retrieve, and delete event registrants. This provides a low volume synchronous option to go along with the Bulk API endpoints to be used for large volumes. Learn more

Example: Create an event registrant

Create a new event registrant and map to contact for the event with Id #1260:

POST api/REST/2.0/data/eventRegistration/1260/instance
							Content-Type: application/json

Request body:

{
								"contactId": "1653175",
								"fieldValues": [
								{
								"id": "3958",
								"value": "sally@oracle.com"
								},
								{
								"id": "3959",
								"value": "Sally"
								},
								{
								"id": "3960",
								"value": "Technology"
								},
								{
								"id": "3962",
								"value": "41547123"
								},
								{
								"id": "3964",
								"value": "North America"
								},
								{
								"id": "3963",
								"value": "2"
								},
								{
								"id": "3961",
								"value": "Yes"
								}
								]
							}

Request response:

{
								"type": "EventRegistrationData",
								"id": "332379",
								"createdAt": "1493240064",
								"name": "sally@oracle.com",
								"updatedAt": "1493240064",
								"contactId": "1653175",
								"customObjectRecordStatus": "Registered",
								"fieldValues": [
								{
								"type": "FieldValue",
								"id": "3958",
								"value": "sally@oracle.com"
								},
								{
								"type": "FieldValue",
								"id": "3959",
								"value": "Sally"
								},
								{
								"type": "FieldValue",
								"id": "3960",
								"value": "Technology"
								},
								{
								"type": "FieldValue",
								"id": "3962",
								"value": "41547123"
								},
								{
								"type": "FieldValue",
								"id": "3964",
								"value": "North America"
								},
								{
								"type": "FieldValue",
								"id": "3963",
								"value": "2"
								},
								{
								"type": "FieldValue",
								"id": "3961",
								"value": "Yes"
								}
								],
								"isMapped": "Yes",
								"uniqueCode": "sally@oracle.com"
							}

Platform notices

When importing invalid data along with valid data that is imported, the sync logs will now indicate the record in the count for statusCode ELQ-00144 that has a message of "Total records with rejected fields." Learn more

Release 487

A list of developer-facing new features, significant recent changes, and platform notices for Oracle Eloqua release 487.

New features

AppCloud Developer Framework

Added the ability to retrieve a low-volume batch of service instances through the AppCloud API. App providers can now retrieve up to 200 service instances in a single call for Action and Decision services. Note that X-HTTP-Method-Override: SEARCH is required in the request header. See the endpoint documentation for Action and Decision services for more information.

Release 486

A list of developer-facing new features, significant recent changes, and platform notices for Oracle Eloqua release 486.

New features

AppCloud Developer Framework

Firehose services can now subscribe to program canvas events. This enhancement provides App providers the ability to develop firehose services that receive notifications for the following program canvas events: Created, Updated, Deleted, Draft, Activated, and Paused. Learn more
Example: Firehose service configured to request all program-related events
For example, if an app has a Firehose service and is configured to request all program-related events. A call to its notification URL could then resemble:
POST https://example.com/firehose { "siteId": 12345678, "assetId": 1234, "assetType": "Program", "eventType": "Created", "eventDate": "02/09/2017 10:27:51", "userId": "2", "userName": "API.User", "siteName": "API.Test", "msgAttributes": { "name": "Example Program", "userculture": "en-US" } }

Platform notices

Support is ending for the EloquaService SOAP API on April 1st, 2017. Learn more

Release 485

A list of developer-facing new features, significant recent changes, and platform notices for Oracle Eloqua release 485.

New features

AppCloud Developer Framework

Increased the canvas cloud step data retention from 30 days to 90 days.

Bulk API

Events

We've added new endpoints to enable importing event registrants. These endpoints were built to replace the same functionality, previously only supported via the SOAP API, which is to be deprecated. Learn more.

Recent changes

Authentication

Improved the behaviour of OAuth when simultaneous requests are sent to refresh an access token.

Release 484

A list of developer-facing new features, significant recent changes, and platform notices for Oracle Eloqua release 484.

New features

AppCloud Developer Framework

The program canvas is now generally available, and app developers can now specify if their service is available for use in contact programs and custom object programs (during service registration, under User Access). We've also added two new service level URL template parameters for action, decision, and feeder services. The EntityType and CustomObjectId parameters support developers wanting to create apps for the program canvas. Learn more

Bulk API

Events

We've added new endpoints that enable developers to discover Events and Event Fields. Learn more

Example: Retrieving fields for an event

Retrieve a list of the first 5 event fields for the event with id # 8:

GET api/bulk/2.0/events/8/fields?limit=5

Request response:

{
								"items": [
								{
								"name": "First Name",
								"internalName": "First_Name1",
								"dataType": "string",
								"defaultValue": "Name",
								"hasReadOnlyConstraint": false,
								"hasNotNullConstraint": false,
								"hasUniquenessConstraint": false,
								"statement": "{{Event[12].Field[55]}}",
								"uri": "/events/12/fields/55"
								},
								{
								"name": "Last Name",
								"internalName": "Last_Name1",
								"dataType": "string",
								"defaultValue": "Last Name",
								"hasReadOnlyConstraint": false,
								"hasNotNullConstraint": false,
								"hasUniquenessConstraint": false,
								"statement": "{{Event[12].Field[56]}}",
								"uri": "/events/12/fields/56"
								},
								{
								"name": "Email Address",
								"internalName": "Email_Address1",
								"dataType": "string",
								"defaultValue": "Email Address",
								"hasReadOnlyConstraint": false,
								"hasNotNullConstraint": false,
								"hasUniquenessConstraint": false,
								"statement": "{{Event[12].Field[57]}}",
								"uri": "/events/12/fields/57"
								},
								{
								"name": "Job Role",
								"internalName": "Job_Role1",
								"dataType": "string",
								"defaultValue": "Job Role",
								"hasReadOnlyConstraint": false,
								"hasNotNullConstraint": false,
								"hasUniquenessConstraint": false,
								"statement": "{{Event[12].Field[58]}}",
								"uri": "/events/12/fields/58"
								},
								{
								"name": "Industry",
								"internalName": "Industry1",
								"dataType": "string",
								"defaultValue": "Industry",
								"hasReadOnlyConstraint": false,
								"hasNotNullConstraint": false,
								"hasUniquenessConstraint": false,
								"statement": "{{Event[12].Field[59]}}",
								"uri": "/events/12/fields/59"
								}
								],
								"totalResults": 8,
								"limit": 5,
								"offset": 0,
								"count": 5,
								"hasMore": true
							}

We've added new endpoints to enable exporting event registrants. These endpoints were built to replace the same functionality, previously only supported via the SOAP API, which is to be deprecated. Learn more.

Endpoints to enable importing event registrants will be available in release 485.

Exports

You can now use the areSystemTimestampsInUTC request parameter to export system timestamp fields into Coordinated Universal Time (UTC). By default, system timestamp fields are expressed in Eastern Time (ET). By setting areSystemTimestampsInUTC to true, you can export system timestamp fields in UTC on contacts, custom objects, accounts, activity records, and events.

Recent changes

Application API

When retrieving campaigns, the memberCount property will now only appear if the request depth is set to partial or complete. Previously, memberCount was included if the request depth was set to minimal, partial, or complete. Learn more

Eloqua's APIs will now correctly return a value of true for hasNotNullConstraint (Bulk API) and isRequired (Application API) in Eloqua instances where email addresses are required for contacts. Previously when retrieving the email address field, Eloqua's APIs would incorrectly indicate that email address field was not required by returning a value of false for hasNotNullConstraint in the Bulk API and isRequired in the Application API.

Platform notices

The Oracle Eloqua URL standardization that was to not renew the old certificates for secure.eloqua.com for POD 1 and www.02.secure.eloqua.com for POD 2 has been postponed indefinitely.

The certificates in question will be renewed so that traffic from the URLs with "legacy" naming conventions will continue to be redirected appropriately and there will be no disruption on your end. As there is no longer an expiration date, any calls (API calls, redirects, etc) to the old URLs will continue to work.

Learn more

Release 483

A list of developer-facing new features, significant recent changes, and platform notices for Oracle Eloqua release 483.

New features

Application API

Accounts

We've added a new endpoint which retrieves account information for up to 200 accounts per request, searched by account id. Developers can now search on a low volume of accounts to retrieve their account information. This endpoint was built to replace the same functionality, previously only supported via the SOAP API, which is to be deprecated. Note that X-HTTP-Method-Override: SEARCH is required in the request header, and the depth parameter must be set in the response body instead of as a query string parameter. Learn more

We've added a new endpoint to retrieve a list of all of the account groups that an account is a member of. Learn more

Account groups

You can now use the account groups API to create, update, retrieve, and delete account groups. Learn more

Contacts

We've added a new endpoint to retrieve contact information for up to 200 contacts per request, searched by contact id. Developers can now search on a low volume of contacts to retrieve their contact information. This endpoint was built to replace the same functionality, previously only supported via the SOAP API, which is to be deprecated. Note that X-HTTP-Method-Override: SEARCH is required in the request header, and the depth parameter must be set in the response body instead of as a query string parameter. Learn more

We've added a new endpoint to retrieve a list of all of the contact lists that a contact is a member of. Learn more

Signature rules

You can now use the Signature Rules API to retrieve a single signature rule asset or a list of signature rules. Learn more

Visitor profiles

We've added a new endpoint to retrieve visitor profile fields. You can now retrieve the fields and their field values associated to your website visitors. This was built to replace the same functionality, previously only supported via the SOAP API, which is to be deprecated. Learn more

Example: Retrieve a list of all of the visitor profile fields in your database

GET api/REST/2.0/assets/visitor/fields

Request response:

{
								"elements": [{
								"type": "ProfileField",
								"id": "264",
								"name": "Customer Guid",
								"dataType": "text",
								"internalName": "CustomerGuid",
								"length": "50"
								}, {
								"type": "ProfileField",
								"id": "157",
								"name": "Browser",
								"dataType": "text",
								"internalName": "V_Browser_Type",
								"length": "50"
								}, {
								"type": "ProfileField",
								"id": "256",
								"name": "City (from IP)",
								"dataType": "text",
								"internalName": "V_CityFromIP",
								"length": "50"
								}, {
								"type": "ProfileField",
								"id": "210",
								"name": "Company DNS Name",
								"dataType": "text",
								"internalName": "V_CompanyDNSName",
								"length": "50"
								}, {
								"type": "ProfileField",
								"id": "246",
								"name": "Company (from IP)",
								"dataType": "largeText",
								"internalName": "V_CompanyNameFromIP1",
								"length": "200"
								}, {
								"type": "ProfileField",
								"id": "245",
								"name": "Country (from IP)",
								"dataType": "text",
								"internalName": "V_CountryFromIP",
								"length": "50"
								}, {
								"type": "ProfileField",
								"id": "241",
								"name": "Country (from DNS)",
								"dataType": "text",
								"internalName": "V_CountryName",
								"length": "50"
								}, {
								"type": "ProfileField",
								"id": "169",
								"name": "Current Total Pages",
								"dataType": "number",
								"internalName": "V_Current_Total_Pages",
								"length": "4"
								}, {
								"type": "ProfileField",
								"id": "168",
								"name": "Current Visit Length",
								"dataType": "number",
								"internalName": "V_Current_Visit_Length",
								"length": "4"
								}, {
								"type": "ProfileField",
								"id": "217",
								"name": "First Page In Visit",
								"dataType": "largeText",
								"internalName": "V_FirstPageInVisit",
								"length": "200"
								}, {
								"type": "ProfileField",
								"id": "212",
								"name": "First Visit Date and Time",
								"dataType": "date",
								"internalName": "V_FirstVisitDateAndTime",
								"length": "8"
								}, {
								"type": "ProfileField",
								"id": "160",
								"name": "Internet Site",
								"dataType": "text",
								"internalName": "V_HostName",
								"length": "50"
								}, {
								"type": "ProfileField",
								"id": "162",
								"name": "IPAddress",
								"dataType": "text",
								"internalName": "V_IPAddress",
								"length": "50"
								}, {
								"type": "ProfileField",
								"id": "254",
								"name": "ISP (from IP)",
								"dataType": "largeText",
								"internalName": "V_ISPFromIP",
								"length": "200"
								}, {
								"type": "ProfileField",
								"id": "231",
								"name": "Last Page In Visit",
								"dataType": "text",
								"internalName": "V_LastPageInVisit",
								"length": "50"
								}, {
								"type": "ProfileField",
								"id": "232",
								"name": "Last Visit Date and Time",
								"dataType": "date",
								"internalName": "V_LastVisitDateAndTime",
								"length": "8"
								}, {
								"type": "ProfileField",
								"id": "258",
								"name": "Latitude (from IP)",
								"dataType": "text",
								"internalName": "V_LatitudeFromIP",
								"length": "50"
								}, {
								"type": "ProfileField",
								"id": "259",
								"name": "Longitude (from IP)",
								"dataType": "text",
								"internalName": "V_LongitudeFromIP",
								"length": "50"
								}, {
								"type": "ProfileField",
								"id": "167",
								"name": "Name",
								"dataType": "text",
								"internalName": "V_Name",
								"length": "50"
								}, {
								"type": "ProfileField",
								"id": "255",
								"name": "State/Province (from IP)",
								"dataType": "text",
								"internalName": "V_ProvinceFromIP",
								"length": "50"
								}, {
								"type": "ProfileField",
								"id": "240",
								"name": "Time Zone",
								"dataType": "text",
								"internalName": "V_TimeZone",
								"length": "50"
								}, {
								"type": "ProfileField",
								"id": "239",
								"name": "Time Zone Offset from GMT",
								"dataType": "number",
								"internalName": "V_TimeZoneOffsetMin",
								"length": "4"
								}, {
								"type": "ProfileField",
								"id": "164",
								"name": "Total Pages",
								"dataType": "number",
								"internalName": "V_Total_Pages",
								"length": "4"
								}, {
								"type": "ProfileField",
								"id": "165",
								"name": "Total Time",
								"dataType": "number",
								"internalName": "V_Total_Time",
								"length": "4"
								}, {
								"type": "ProfileField",
								"id": "166",
								"name": "Total Visits",
								"dataType": "number",
								"internalName": "V_Total_Visits",
								"length": "4"
								}, {
								"type": "ProfileField",
								"id": "257",
								"name": "Zip Code (from IP)",
								"dataType": "text",
								"internalName": "V_ZipCodeFromIP",
								"length": "50"
								}],
								"page": 1,
								"pageSize": 1000,
								"total": 26
							}

Platform notices

We are modifying the Eloqua application API endpoints used to retrieve Campaigns, so that memberCount will now only appear if the request depth is set to partial or complete. Currently, memberCount is included if the request depth is set to minimal, partial, or complete. This change will be implemented in the Eloqua 484 release. Learn more
Update: The Oracle Eloqua URL standardization that was to not renew the old certificates for secure.eloqua.com for POD 1 and www.02.secure.eloqua.com for POD 2 has been postponed indefinately.

The certificates in question will be renewed so that traffic from the URLs with "legacy" naming conventions will continue to be redirected appropriately and there will be no disruption on your end. As there is no longer an expiration date, any calls (API calls, redirects, etc) to the old URLs will continue to work.

Learn more

Effective this coming Fall (2016), we will not be renewing the old certificates for secure.eloqua.com for POD 1 and www.02.secure.eloqua.com for POD 2, and as such clients must ensure they're pointing to the newer, updated, application URLs before they expire. Failure to do so before the certification expiration dates will result in any API calls to the old URLs failing. Certificate Expiration Dates:
- POD 1 - Friday, November 18, 2016 for secure.eloqua.com
  - https://secure.eloqua.com changes to https://secure.p01.eloqua.com.
- POD 2 - Sunday, December 11, 2016 for www02.secure.eloqua.com
  - https://www02.secure.eloqua.com changes to https://secure.p02.eloqua.com. Learn more

Release 482

A list of developer-facing new features, significant recent changes, and platform notices for Oracle Eloqua release 482.

New features

Application API

Added RESTful API support for Email sending to a single, or low volume of contacts, as well as the retrieval of associated deployment information. This was built to replace the same functionality, previously only supported via the SOAP API, which is to be deprecated.

Example: Create and send an email deployment for an existing email asset to a single contact

POST /assets/email/deployment

Request body:

{
								"type": "EmailTestDeployment",
								"name": "REST Test 01",
								"contactId": "1",
								"email": {
								"type": "Email",
								"id": "100",
								"name": "test01"
								},
								"sendOptions": {
								"allowResend": "true",
								"allowSendToUnsubscribe": "false"
								}
							}

Request response:

{
								"type": "EmailTestDeployment",
								"currentStatus": "normal",
								"id": "4",
								"depth": "complete",
								"name": "REST Test 01",
								"permissions": [
								"Retrieve",
								"SetSecurity",
								"Delete",
								"Update",
								"Activate"
								],
								"email": {
								"type": "Email",
								"x_e10_previewUrl": "https://p03.eloquapreview.com/Preview.aspx?siteId=238011564&userGuid=a2475311-77bb-41e6-9db1-45c8c6402efa",
								"x_e10_previewExpiryDate": "1468620740",
								"x_e10_isTemplate": "false",
								"x_e10_createdAt": "1468620436",
								"x_e10_createdBy": "11",
								"currentStatus": "Draft",
								"id": "100",
								"createdAt": "1468620389",
								"createdBy": "11",
								"depth": "complete",
								"folderId": "42",
								"name": "Test_Email",
								"permissions": [
								"Retrieve",
								"SetSecurity",
								"Delete",
								"Update"
								],
								"updatedAt": "1468620436",
								"updatedBy": "11",
								"archive": "false",
								"bounceBackEmail": "APIUserSandbox@s238011564.m.en25.com",
								"contentSections": [],
								"dynamicContents": [],
								"emailFooterId": "1",
								"emailGroupId": "4",
								"emailHeaderId": "1",
								"encodingId": "3",
								"fieldMerges": [],
								"forms": [],
								"htmlContent": {
								"type": "RawHtmlContent",
								"contentSource": "upload",
								"html": "<!DOCTYPE html> \r\n<html>\r\n  <head>  </head>\r\n  <body>\r\n    <p>Test Email</p>\r\n  </body> \r\n</html>"
								},
								"hyperlinks": [],
								"images": [],
								"isContentProtected": "false",
								"isPlainTextEditable": "false",
								"isPrivate": "False",
								"isTracked": "true",
								"layout": "{}",
								"plainText": "\r\nTest Email\r\n\r\n",
								"renderMode": "Flow",
								"replyToEmail": "API.User@test.oracle.com",
								"replyToName": "API User",
								"sendPlainTextOnly": "false",
								"senderEmail": "API.User@test.oracle.com",
								"senderName": "API User",
								"style": "{}",
								"subject": "Test"
								},
								"failedSendCount": "0",
								"successfulSendCount": "0",
								"contactId": "1",
								"sendOptions": {
								"type": "EmailSendOptions",
								"allowResend": "true",
								"allowSendToBounceback": "false",
								"allowSendToGroupUnsubscribe": "true",
								"allowSendToMasterExclude": "false",
								"allowSendToUnsubscribe": "false"
								}
							}

AppCloud Developer Framework

Added an endpoint to retrieve an app's outbound logs. Leveraging this endpoint to view outbound logs enables app providers to retrieve logs for apps across different pods, while the logs page in Eloqua's web interface is limited only to displaying outbound requests for your instance and other clients on your pod. Learn more

Authentication

Modified the behaviour of OAuth so that each time a new access token is requested, a new refresh token will be returned. Learn more

Documentation

We've launched our new API reference documentation at a new location in a new format. Our API reference documentation can now be found at: http://docs.oracle.com/cloud/latest/marketingcs_gs/OMCAC/

See the New API Documentation Announcement to learn more.

Recent changes

Bulk API

Including the read-only field updatedAt was causing imports to fail in two scenarios:
- In a custom object import definition and data upload.
- In a custom object import definition when updatedAt was left out of the data upload.
Now, when including updatedAt in a custom object import definition and data upload, the import succeeds with the read-only field and data uploaded to the field being ignored. Also, including updatedAt in a custom object import definition and leaving the field out of the data upload, will cause the import to return a warning, but still import the data successfully.
Setting the import definition request parameter isUpdatingMultipleMatchedRecords to true resulted in newly created records appearing under created and updated in the logs.

Platform notices

EloquaService API will remain supported until April 1st, 2017, with basic availability and security fixes only. Learn more
ExternalActionService (aka Cloud Connector API) will continue to be supported indefinitely.