Oracle Fusion Cloud connector

Beta — this connector is in beta. Functionality and resource coverage may change.

At a Glance

Difficulty: 🔧ADVANCEDCustom Server-to-Server Auth + Multi-Step Per-Consumer Setup Across Oracle Admin Tools
Authentication: OAuth 2.0Server-to-server OAuth 2.0 client credentials in the consumer's OCI IAM identity domain — no browser consent.
Webhooks: No webhooks — neither native nor virtual; poll the list endpoints, where journals and invoices support an updated-since filter.
Partnership Required: No(Oracle PartnerNetwork's optional Oracle Validated track is for marketing a commercial integration, not for building or connecting one.)
Partnership Application: Oracle PartnerNetwork↗
Apideck Credentials: Not available(Every connection uses the consumer's own Oracle tenant and OAuth application.)
Costs: No separate per-call API charge documented by Oracle — API access comes with the Fusion subscription itself.
Sandbox Availability: Not available(Existing customers provision an Additional Test Environment pod against their subscription; the in-app Sandbox feature isolates UI config only.)
Account Type Required: Oracle Fusion Cloud ERP / Financials tenant with a General Ledger, plus administrative access to its identity domain.
Consumer Access Level: Oracle administrator with user, role, data-access and scheduled-process administration rights — a regular Fusion user cannot self-serve the connection.
Rate Limits: Oracle publishes no rate-limit figures; throttling is per identity domain, shared by every integration on it. Requests time out at 5 minutes.

Responsibility matrix

Task	You (Customer)	Your Consumer	Apideck
Enable the Connector & Hand the Connection Guide to the Oracle Administrator	✓	—	Connection guide provided
Register OAuth Application	—	✓	Instructions provided
Create Integration User, Grant Roles & Data Access, Run Scheduled Processes	—	✓	—
Configure Receivables for Invoice Creation	—	✓ (if using invoices)	—
Provide Host, Identity-Domain Credentials & Ledger Settings	—	✓	Vault connection form & guide
Mint & Refresh Tokens, Submit Journal Imports, Build Invoice Lines	—	—	✓
Post Imported Journals & Correct Completed Invoices in Oracle	—	✓	—

Environments

Single environment: Testing and production use the same kind of credentials: a connection points at one Fusion pod (Host and Data Center) and its identity domain. Test against a consumer's Additional Test Environment pod, which has its own OAuth application and integration user — there is no Apideck shared Oracle tenant. Caution: journal imports and invoice creates on a production pod create real records (journals arrive Unposted).

🚨Important to Know About Oracle Fusion Cloud

Invoices need Oracle Receivables configuration on the tenant before a single create works (business unit, transaction source, memo lines, open Receivables periods); the General Ledger path alone does not unlock them. Budget a second setup pass with the Oracle administrator.
Every role or data-access change is invisible to the API until two Oracle scheduled processes have run, in order; the connection validates green even for a user with no data access, so an empty list can mean a pending grant rather than an empty ledger.
One connection covers exactly one General Ledger; a tenant with several ledgers needs one connection per ledger, each with its own ledger and data-access settings.
Journal creation can fail with a 503 for up to about thirty minutes while every read keeps working, because Oracle's scheduler intermittently refuses the connection's client-credentials token; retry later.

⚠️

12 gotchas across 7 resources

Connector-specific behaviors and limitations to be aware of

📦

7 supported resources

View field mappings, supported operations, and schema details