The API Report CardAPI Index
THE API REPORT CARD / Marketing & Sales / Oracle Eloqua
Oracle Eloqua

Oracle Eloqua API

Enterprise B2B Marketing Automation · oracle.com

Two self-serve REST families are documented: the synchronous Application API and the job-based Bulk API for high volume, with OAuth 2.0 auth. Throttling is the real constraint: roughly 10 to 20 concurrent requests and about 50 per minute, with 429s in peak sync windows.

Last verified: July 2026Marketing & Sales
API GRADE
C
VERIFIED JUL 2026

SCORECARD

ExistenceGOODTwo documented REST families: the synchronous Application API (1.0 and 2.0) and the asynchronous, job-based Bulk API.
AccessGOODSelf-serve for customers, with the certified AppCloud program adding Firehose events and Campaign Canvas extensions.
CoverageMIXEDCRUD spans contacts, campaigns, and assets, but search caps at 200 records per call and some lists at 1,000 items.
AuthGOODOAuth 2.0 with three flows including Authorization Code; legacy HTTP Basic still works but is deprecated for production.
Docs & DXGOODBoth API families are documented on docs.oracle.com; the AppCloud framework covers certified partner extensions.
StabilityMIXEDThrottling is real: roughly 10 to 20 concurrent requests and about 50 per minute, with 429s in peak sync windows.
MORE FROM THE REPORT CARD
ActiveCampaignAAct-OnC+17hatsC6senseC
Supergood: Oracle Eloqua has an API, with gaps. We cover what it's missing: stable endpoints, normalized JSON, managed auth.

Frequently asked questions

Oracle Eloqua scores C on the API Report Card. Two self-serve REST families are documented: the synchronous Application API and the job-based Bulk API for high volume, with OAuth 2.0 auth. Throttling is the real constraint: roughly 10 to 20 concurrent requests and about 50 per minute, with 429s in peak sync windows.

Tried to integrate with Oracle Eloqua?
SOURCES
Concurrent request limits are tight, typical concurrent request limits for the REST API range from 10 to 20 concurrent requests depending on subscription tier; exceeding returns HTTP 429 errors cleverence.com ↗
Per-minute throttling caps REST API at approximately 50 requests/minute, leading to throttling and potential service unavailability during peak ETL/sync windows vantagepoint.io ↗
API surface is split between Application API (synchronous, low-volume, version 1.0 and 2.0 with inconsistent endpoint coverage) and Bulk API (asynchronous job-based, high-volume), developers must learn both and pick correctly per use case or face throttling 4thoughtmarketing.com ↗
Bulk API POST requests to data endpoints cannot exceed 32 MB, forcing chunking logic for large imports docs.oracle.com ↗
Application API search endpoints (Accounts, Contacts) cap results at 200 records per call, requiring pagination loops that quickly burn concurrent-request budget docs.oracle.com ↗
Hard 1,000-item limit on certain Application API list/search responses requires Bulk API fallback for full extracts github.com ↗
No standalone native webhook stream for general object changes, change-detection requires polling Bulk API export jobs (Contact Activity, Account, CDO) or building an AppCloud App that subscribes to Firehose, which is gated to certified partners through the developer.eloqua.com program docs.oracle.com ↗
Pod-specific base URL discovery, the login.eloqua.com endpoint must be called at session start to determine the customer's POD (POD1-POD8) base URL; hard-coding a base URL breaks when Oracle migrates the customer between pods docs.oracle.com ↗
HTTP Basic Auth is still supported but deprecated for production use; migration to OAuth 2.0 is recommended and the Oracle Sales Integration App for Eloqua just gained OAuth 2.0 support in the 25C release (2025), implying many production integrations are still on Basic Auth and need to be rewritten docs.oracle.com ↗
Insight reporting API access is gated separately and historically less complete than the operational REST APIs, forcing dashboard builders to either screen-scrape or pay for AppCloud-partner reporting layers docs.oracle.com ↗
Outdated user interface, the UI 'feels outdated and not very intuitive,' navigation isn't always logical, and common everyday tasks take more clicks than they should g2.com ↗
Steep learning curve cited as the biggest drawback, Eloqua is powerful but requires significant training; backend settings, campaign structure, and contact database configurations have so many layered menus and technical options that mastery takes months gartner.com ↗
Customer support quality has declined, over 75% of users referencing support report customer service 'isn't up to the mark' and often responds based on issue severity; the customer success team has shown a significant decline over the last few years peerspot.com ↗
Infrequent feature updates and outdated reporting are a cause for concern according to all users mentioning this aspect, Eloqua lacks modern features such as built-in WhatsApp marketing and SMS functionality available in newer platforms capterra.com ↗
High cost relative to functionality, 86% of user feedback on cost says Eloqua is not cost-effective; entry tier ~$2k/mo, enterprise ~$40k-$100k+/mo for 1M+ contacts, plus $15k-$75k implementation fees pricingnow.com ↗
Integration with third-party apps often needs additional middleware or custom coding; automation workflows can be difficult to configure and adjust research.com ↗
Mandatory certified consulting partner for implementation, nearly every customer hires an Eloqua-certified agency (Relationship One, 4Thought Marketing, etc.) at $150-$250/hr for setup, ongoing optimization, and integration work redresscompliance.com ↗
Reporting via Insight (OBIEE-based) is slow, requires extensive setup to get useful insights, and many users report simple tasks take too many steps and require workarounds softwareadvice.com ↗
Oracle's strategic shift toward Oracle Fusion Marketing / Oracle Unity CDP creates uncertainty about long-term Eloqua roadmap investment, perceived as a 'maintenance mode' product peerspot.com ↗
Salesforce / Dynamics / Oracle CX Sales connector sync issues, sync queue backlogs, field-mapping conflicts, and duplicate-contact handling are common Mar Ops operational pain points g2.com ↗
© Supergood Systems, Inc.