Included because Eloqua separates interactive campaign and data CRUD, staged high-volume imports and exports, and read-only reporting into distinct APIs under enterprise security-group and contact-level permissions.
Concrete capability record
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
Contacts and fields, accounts, contact lists and segments, custom objects and records, activities and events, campaign responses, opportunities, campaigns, emails and groups, content sections, landing pages, forms, images, and bulk synchronization definitions.
Retrieve permitted data and campaign assets through the Application API, stage and export large contact or business-object datasets through Bulk, and query campaign-analysis subject areas through the GET-only Reporting API.
Create, update, or delete supported data and campaign resources through the Application API, and import high-volume contact, account, custom-object, activity, event, campaign-response, or opportunity data through staged Bulk synchronizations.
OAuth 2.0 is preferred, while HTTP Basic is also supported. Effective access inherits the Eloqua user's security group, contact-level restrictions, field and secondary-asset permissions; Bulk supports two-legged OAuth for second-party apps and three-legged OAuth for AppCloud apps.
Keep Application, Bulk, and Reporting operations distinct; bind each request to the discovered instance base URL and least-privilege actor, and require a reviewed field map and record count before a Bulk synchronization pushes staged data into Eloqua.
No Eloqua-native provider MCP is documented. The Reporting API is read-only, base URLs are instance-specific rather than static, and Bulk requires a definition, staging, and synchronization or export retrieval sequence.
Agent access
Support: Bridge
Read scope: No first-party MCP read surface verified.
Write scope: No first-party MCP write surface verified.
Authentication: Not applicable to a first-party MCP provider.
Approval boundary: Any customer-built adapter must define its own approval and confirmation controls.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Proposed customer-shaped experiences
The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that Oracle ships them.
Evidence and dates
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
First-party API reference or API overview recorded for this platform.
Targeted first-party core-access review
First-party developer documentation or platform overview.
Inventory source: structurally normalized; content was not individually reopened in this pass.
First-party product homepage used to confirm product identity and current positioning.
Inventory source: structurally normalized; content was not individually reopened in this pass.
Oracle Integration can expose Eloqua adapter workflows as MCP tools, but no Eloqua-native provider server was verified.
Full-profile first-party re-verification on 2026-07-12; see the private audit ledger.
Tied to cited first-party evidence reviewed for this profile.
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
System role, maturity interpretation, and architectural boundary.
Interface patterns and compositions—not vendor product claims.
