Oracle Eloqua Marketing Cloud Service REST API

Name: Oracle Eloqua Marketing Cloud Service REST API API
Brand: Oracle Eloqua Marketing Cloud Service REST API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMarketingMarketing Automationbearer, basic358 EndpointsREST

For Agents

Connect the Oracle Eloqua Marketing Cloud Service REST API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Oracle Eloqua Marketing Cloud Service REST API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Oracle Eloqua Marketing Cloud Service REST API API.

Create and update contact records in Eloqua including custom fields

Search and segment contacts by activity, list, or custom criteria

Manage campaigns including launching, scheduling, and monitoring status

Send and track Eloqua emails and retrieve engagement metrics

GET STARTED

Start building with Oracle Eloqua Marketing Cloud Service REST API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Oracle Eloqua Marketing Cloud Service REST API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Oracle Eloqua Marketing Cloud Service REST API, keeping it validated and agent-ready. The Eloqua REST API exposes contacts, accounts, campaigns, emails, forms, and bulk import and export jobs across Application v1.0, Application v2.0, and Bulk v2.0 surfaces. It is the integration backbone for B2B marketers that need to sync large CRM populations, manage nurture campaigns, and pull engagement activity into a data warehouse on a schedule.

Use Cases

Patterns agents use Oracle Eloqua Marketing Cloud Service REST API API for, with concrete tasks.

★ CRM-to-Eloqua Contact Sync

Keep an external CRM and Eloqua aligned by mirroring contact records and lead status changes between the two systems. The Application REST API exposes contacts and accounts with full custom-field support so the integration can map every Salesforce or HubSpot field to its Eloqua counterpart and reconcile in either direction.

POST /api/REST/1.0/data/contact for new CRM leads and PATCH the Eloqua contact when the source record changes

Campaign Engagement Warehouse

Pull email opens, clicks, form submits, and visit data out of Eloqua and load it into a data warehouse for cross-channel attribution. The Bulk v2.0 surface exists exactly for this — it is built for high-volume exports of activities, contacts, and accounts on a schedule.

Create a bulk export job for contact activities since the last watermark, poll until it completes, then download the result

Form-Driven Lead Capture and Routing

Use Eloqua forms as the lead-capture layer for landing pages and route incoming submissions through the API to scoring rules and nurture campaigns. The Application REST API exposes form definitions and submissions, so an integration can add submissions and trigger downstream campaign membership.

POST a new form submission to Eloqua and add the resulting contact to a nurture program

Marketing Operations Reporting

Generate marketing operations dashboards by combining campaign metadata from the Application API with engagement counts from the Bulk API. Marketing ops teams use this pattern to report campaign throughput, deliverability, and pipeline contribution without touching the Eloqua UI.

GET active campaigns from the Application API and bulk-export their email activity, then render a weekly ops report

Agent-Driven Eloqua Operations via Jentic

An AI assistant for marketing ops can search Eloqua contacts, launch campaigns, and queue bulk exports through Jentic. The agent handles natural-language intents and Jentic resolves them to the right Application or Bulk endpoint without leaking Basic Auth credentials.

Search Jentic for 'create an Eloqua contact', load the POST /api/REST/1.0/data/contact operation, and execute with the lead's details

Key Endpoints

358 endpoints — jentic publishes the only available openapi specification for oracle eloqua marketing cloud service rest api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/api/REST/1.0/data/contacts

List contacts

POST

/api/REST/1.0/data/contact

Create a contact

GET

/api/REST/1.0/data/contact/{id}

Retrieve a contact

GET

/api/REST/1.0/data/accounts

List accounts

GET

/api/REST/1.0/data/account/{id}

Retrieve an account

GET

/api/REST/1.0/data/activities/contact/{id}

Retrieve activities for a contact

GET

/api/REST/1.0/data/contacts

List contacts

POST

/api/REST/1.0/data/contact

Create a contact

GET

/api/REST/1.0/data/contact/{id}

Retrieve a contact

GET

/api/REST/1.0/data/accounts

List accounts

GET

/api/REST/1.0/data/account/{id}

Retrieve an account

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Eloqua Bearer tokens and Basic Auth credentials are stored encrypted in the Jentic vault per Eloqua instance. Agents receive scoped sessions and never touch the underlying token or password.

Intent-based discovery

Agents search by intent like 'create an Eloqua contact' or 'export campaign activity', and Jentic returns the matching Application or Bulk operation with its parameter schema.

Time to first call

Direct Eloqua integration: 1-2 weeks to handle pod discovery, OAuth, the Application/Bulk surface split, and bulk job polling. Through Jentic: under 1 hour from signup to first contact create or activity export.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

HubSpot Marketing Events API

HubSpot's marketing automation surface targets SMB and mid-market more than Eloqua's enterprise B2B fit

Choose HubSpot for SMB and mid-market marketing automation; Eloqua is the right choice for enterprise B2B with deep CRM integration.

Alternative

Mailchimp Marketing API

SMB-focused email and marketing automation API with a much smaller surface than Eloqua

Pick Mailchimp for SMB email marketing and basic automation; pick Eloqua for enterprise B2B with deep account-based marketing.

Complementary

Salesforce REST API

CRM commonly synced with Eloqua for B2B lead-to-opportunity flow

Use Salesforce alongside Eloqua to keep accounts and contacts aligned across the CRM and the marketing automation system.

FAQs

Specific to using Oracle Eloqua Marketing Cloud Service REST API API through Jentic.

Why is there no official OpenAPI spec for Oracle Eloqua Marketing Cloud Service REST API?

Oracle does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Oracle Eloqua Marketing Cloud Service REST API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Oracle Eloqua REST API use?

The spec declares both bearerAuth (HTTP Bearer) and basicAuth (HTTP Basic) schemes. Production integrations use Bearer tokens issued via Eloqua's OAuth flow, with Basic Auth available for legacy and bulk transfer scenarios. Jentic stores either credential type encrypted in the vault and hands the agent a scoped session.

Can I bulk export contact activity from Eloqua?

Yes. The Bulk Activities and Bulk Contacts tag groups expose multi-step jobs: create the export definition, sync the data, then download the result. This is the supported path for high-volume engagement exports rather than paginating the Application API.

Does the spec cover both Application v1.0 and v2.0 plus the Bulk API?

Yes. Tag groups for Accounts v1.0, Accounts v2.0, Activities v1.0, Activities v2.0, Bulk Accounts, Bulk Activities, Bulk Campaign Responses, and Bulk Contacts are all present in the spec, so integrations can pick the surface that matches their data shape and volume.

What is the base URL pattern for Eloqua API calls?

https://{instance}.eloqua.com where {instance} is the customer's Eloqua pod (for example secure.p01 or secure.p02). The pod is returned by Eloqua's login URL discovery call and must be used for every subsequent API request.

How do I create an Eloqua contact through Jentic?

Install the SDK with pip install jentic, then search Jentic for 'create an Eloqua contact'. Jentic returns the POST /api/REST/1.0/data/contact operation with its schema; load it, supply the contact payload, and execute. Sign up at https://app.jentic.com/sign-up.