Oracle Fusion Technical: Reports, Data, Integrations and Extensions · Module 10 · REST and SOAP: calling Fusion, and being called
What Fusion exposes, and what it does not
Lesson 98 of 177 · 2 min
Find out what exists BEFORE you promise a client something. That is the practical content of this lesson and it takes twenty minutes. REST resources cover most of what modern Fusion does, organised by business object, with the usual verbs and a documented payload. SOAP services cover a different and partly overlapping set — older, wider in some modules, and the only route to certain operations. AND SOME OPERATIONS EXIST FOR NEITHER. That is the sentence people skip. Not everything a user can do on a screen is exposed as a service; some processes are submitted through the scheduler rather than called, and some objects are loadable by file and not writable by API. "It is in the UI, so there must be a service" is false, and it is expensive to discover late. The check, in order. Look for the object in the REST API reference for your release.…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Oracle Fusion Technical: Reports, Data, Integrations and Extensions, with a certificate on completion and a fourteen-day refund window.
In this module: Module 10 · REST and SOAP: calling Fusion, and being called
- 1What Fusion exposes, and what it does not
- 2REST vs SOAP: choosing without arguingFree preview
- 3Authentication and the service account
- 4Reading the REST API catalogue
- 5Your first call, and its error
- 6Payloads, child resources and partial updates
- 7Bulk operations and rate limits
- 8Fusion calling out: business events
- 9Idempotency and retries
- 10Versioning and surviving a quarterly update
- 11What breaks: five integration failures
- 12Lab briefing · Read, write and break an integration