Reading the REST API catalogue

Find the resource, the operation and the payload shape — and check the release before you trust any of it. The catalogue is organised by product family, then by resource. Each resource lists its operations, its attributes with their types and whether they are required, its child resources, and an example payload. Read the ATTRIBUTE list rather than the example: the example shows a minimal call, and the attributes tell you what else exists and which of it you must supply. TELLING A CURRENT PAGE FROM ONE DESCRIBING A RELEASE YOU ARE NOT ON is the same trap as Module 1's documentation lesson, and it costs more here. A payload that was valid two releases ago may be missing a now-required attribute, and the failure is a rejection naming a field you did not know existed. Every page names its release. Check it against your environment, every time. Search engines…

In this module: Module 10 · REST and SOAP: calling Fusion, and being called

1. 1What Fusion exposes, and what it does not
2. 2REST vs SOAP: choosing without arguingFree preview
3. 3Authentication and the service account
4. 4Reading the REST API catalogue
5. 5Your first call, and its error
6. 6Payloads, child resources and partial updates
7. 7Bulk operations and rate limits
8. 8Fusion calling out: business events
9. 9Idempotency and retries
10. 10Versioning and surviving a quarterly update
11. 11What breaks: five integration failures
12. 12Lab briefing · Read, write and break an integration