Eloqua

This documentation for the Eloqua integration describes the technical capabilities of this integration, including authorization, scopes/permissions, and utilized endpoints. For more information on how to integrate Eloqua, visit our connection instructions.

Version

This integration utilizes the Eloqua REST API v1.0 or v2.0.

Base URL

The base URL used for all Eloqua API endpoints contains the Pod:

https://secure.pod.eloqua.com/api/rest

---

Authentication & Authorization

The DataGrail Eloqua integration connects using OAuth 2.0 with the following credentials: Client ID and Client Secret.

Sensitive Credentials

Publicly exposing your API credentials can allow unauthorized access to Eloqua API endpoints by a third party. DataGrail stores your API credentials encrypted and protected.

Scopes

The Eloqua integration requires specific scopes that must be granted in order to function for a given capability.

Scope	Base	Access	Deletion
full	✅	✅	✅

Base Scopes

All base scopes must be granted in order to connect the integration with DataGrail. The remaining scopes are only required if enabling those capabilities

Endpoints Utilized

DataGrail uses the following endpoints to authorize and test the connection:

Method	Endpoint	Purpose	Docs
GET	https://login.eloqua.com/auth/oauth2/authorize	Request authorization
POST	https://login.eloqua.com/auth/oauth2/token	Get and refresh access token
GET	https://login.eloqua.com/id	Validate connection

---

Limits

Limits in Eloqua are calculated using the leaky bucket algorithm. All requests that are made after rate limits have been exceeded are throttled and an HTTP 429 Too Many Requests error is returned. Requests succeed again after enough requests have emptied out of the bucket.

• DataGrail supports requests throttling to stay within 70-80% of specified service rate limits.
• DataGrail processes API responses with HTTP 429 status to interrupt requests, waiting and retrying (using an exponential backoff strategy).

---

Capabilities

Access

DataGrail's Eloqua integration provides Synchronous Access capabilities for the following supported identifier category: Email.

Data Interactions

For Access requests, DataGrail will take the following actions:

1. Search contacts using configured identifiers.
2. For each identified contact:
   • Retrieve contact list memberships.
   • Retrieve a list of activities.
   • Retrieve a list of events.
   • Search event registrants using configured identifiers.

Endpoints Utilized

Method	Endpoint	Purpose	Docs
GET	/1.0/data/activities/contact/contact_id	Retrieve a list of activities
GET	/2.0/assets/eventRegistrations	Retrieve a list of events
GET	/2.0/data/contact/contact_id/membership	Retrieve contact list membership
GET	/2.0/data/contacts	Search a list of contacts
GET	/2.0/data/eventRegistration/event_id/instances	Search event registrants

---

Deletion

DataGrail's Eloqua integration provides Synchronous (Whole Record) Deletion capabilities for the following supported identifier category: Email.

Data Interactions

For Deletion requests, DataGrail will take the following actions:

1. Search contacts using configured identifiers.
2. Update a contact for all detected contacts.

Endpoints Utilized

Method	Endpoint	Purpose	Docs
PUT	/2.0/data/contact/contact_id	Update a contact
GET	/2.0/data/contacts	Search a list of contacts

---