Oracle Eloqua
Oracle Eloqua is a B2B marketing automation platform within Oracle Marketing Cloud that enables marketers to plan and execute multi-channel campaigns, manage leads, and personalize customer engagement across email, web, mobile, and social channels. The platform provides campaign design, lead scoring, segmentation, landing pages, and form processing for B2B demand generation teams. Oracle Eloqua exposes pod-specific REST APIs (Application API and Bulk API) authenticated via OAuth 2.0 or HTTP Basic Authentication, with base URLs resolved per-customer from the login.eloqua.com /id endpoint.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Oracle Eloqua the way a machine reads it — 12 machine-readable artifacts across 8 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Oracle Eloqua scores 29.7/100 (emerging), with a separate agent-readiness read of 41/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Oracle Eloqua
Each block below is one kind of artifact we hold for Oracle Eloqua. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 8
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Oracle Eloqua Application REST API
REST API for managing Eloqua marketing assets, contacts, accounts, campaigns, emails, forms, landing pages, and custom data objects. Base URL is pod-specific and resolved from t...
Oracle Eloqua Bulk API
High-volume import/export REST API for moving large datasets of contacts, accounts, custom objects, and activities in and out of Eloqua. Uses the same OAuth 2.0 and HTTP Basic A...
Oracle Eloqua Accounts API
Manage account records.
Oracle Eloqua Bulk API
Bulk import/export and sync operations.
Oracle Eloqua Campaigns API
Manage marketing campaign assets.
Oracle Eloqua Contacts API
Manage contact records and list membership.
Oracle Eloqua Emails API
Manage email assets and deployments.
Oracle Eloqua Forms API
Manage forms and form submission data.
Scroll within the panel for all 8 ·
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Oracle Eloqua REST API
OPEN COLLECTIONSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Oracle Eloqua — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Commercial 1
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/oracle-eloqua · machine-readable index on apis.io