How-toOracle Fusion Cloud ApplicationsREST APIs / Integration

Oracle Fusion REST API: customers, projects and manufacturing work orders

Question
oracle fusion rest api

Also searched as

  • oracle fusion customer api
  • oracle fusion projects api
  • oracle fusion manufacturing rest api
  • oracle fusion cloud applications api

Short answer

Oracle Fusion Cloud Applications exposes REST resources under a base path per product family, for example /fscmRestApi/resources/<version>/ for supply chain, financials and projects and /crmRestApi/resources/<version>/ for customer data in sales. Authenticate with basic authentication or OAuth, then use q, fields, limit, offset, expand and onlyData to shape results. Resource names differ by product, so confirm them in the REST API documentation for your release.

Applies to: Oracle Fusion Cloud Applications (ERP, SCM, Manufacturing, Project Management, CX). REST version segments such as 11.13.18.05 follow your release, and available resources depend on licensed offerings.

How to call a Fusion REST API

  1. 1Find your pod host name, for example https://<pod>.fa.<region>.oraclecloud.com, and the REST API reference on Oracle Help Center for your release.
  2. 2Create an integration user with the roles needed to view or maintain the target data, and avoid using a named employee account.
  3. 3Pick the resource, such as customers or accounts, projects or work orders, and read its attributes, child resources and finders in the reference.
  4. 4Send a GET to the collection URL with Basic authentication (or an OAuth bearer token) and the header Content-Type: application/json.
  5. 5Filter with q, for example q=WorkOrderNumber='WO1001', and trim the payload with fields and onlyData=true.
  6. 6Page with limit and offset and use totalResults=true when you need a count. Follow the next link in the links array.
  7. 7Use expand to pull child resources in one call instead of looping through each parent.
  8. 8For writes, POST or PATCH a JSON body and handle 4xx validation messages. Use ESS jobs or FBDI for large volumes.

Where the resources live

Fusion REST is organised by product family. Supply chain, manufacturing, procurement, financials and project resources sit under the fscmRestApi path. Sales and customer relationship resources sit under crmRestApi, and human resources under hcmRestApi.

Customer data can appear in more than one place depending on whether you mean a trading partner account in Receivables or an account in Sales. Decide which you need before choosing the endpoint.

GET https://<pod>.fa.<region>.oraclecloud.com/fscmRestApi/resources/11.13.18.05/workOrders?q=WorkOrderNumber='WO1001'&onlyData=true&limit=25

Projects and manufacturing examples

For projects, the project resource exposes project definitions, tasks and related child collections, and expand lets you retrieve tasks along with the project. For manufacturing, the work order resource returns headers with operations, materials and resources as child collections.

Read the describe metadata at the resource URL with /describe to see the exact attributes, finders and supported actions instead of guessing.

Authentication and security

Basic authentication is simple for scripts but ties the integration to a password that expires. OAuth with JWT or an identity provider token is better for production. Whichever you choose, grant the smallest role set that works.

Use the REST-Framework-Version header when you need to pin framework behaviour, and test after each quarterly update because behaviour and resources evolve.

Volume and alternatives

REST suits transactional lookups and small writes. For loading thousands of rows, use File-Based Data Import and the related ESS jobs. For analytics, use BI Publisher or OTBI extracts instead of pulling everything through paging.

Avoid chatty patterns that call one request per child record. Use expand and fields to reduce round trips.

Try it here, free

Oracle Fusion REST API URL Builder

Open full tool

Fill in host, version and resource to generate a Fusion Cloud REST URL with query parameters and a ready curl command.

Common pitfalls

  • !Using an employee account for integration and breaking it on password expiry.
  • !Guessing resource names instead of checking the REST reference and the describe endpoint.
  • !Requesting full payloads with no fields or limit.
  • !Not retesting integrations after quarterly updates.
  • !Using REST for bulk loads that belong in FBDI.

How an ERP-grounded AI assistant handles this

A grounded assistant uses these same REST resources as read-only tools: it picks the resource, builds the q filter, expands the child collection and shows the exact URL it called, so users can check the source of every answer. For organisations with data residency or air-gap concerns, the language model can be hosted privately while it calls the Fusion APIs under a least-privilege integration user, and any create or update is held for human approval.

See ERPray

Frequently asked questions

What is the Oracle Fusion REST API base URL?

It follows your pod host with a product path, for example https://<pod>.fa.<region>.oraclecloud.com/fscmRestApi/resources/<version>/<resource>. The version segment depends on your release.

How do I filter and page results?

Use q for filters, fields to select attributes, limit and offset for paging, and totalResults=true for a count. Follow the next link in the response for the following page.

Can I get work orders from Fusion Manufacturing by REST?

Yes, manufacturing exposes work order resources with operation, material and resource child collections. Confirm the exact resource names and permissions in the reference for your release.

When should I use FBDI instead of REST?

Use File-Based Data Import for bulk loads and migrations because it processes many rows through ESS jobs. Use REST for interactive lookups and small updates.

Related

How-to

Paginate And Authenticate Oracle Fusion REST API Calls Correctly

Oracle Fusion Cloud REST APIs authenticate with HTTP Basic Authentication, an integration user's credentials, over HTTPS by default, and paginate with limit and offset query parameters rather than a page number. Loop on the hasMore flag in the response until it returns false to retrieve a full result set.

How-to

Oracle ERP API Documentation: Where It Is and How to Start

Oracle publishes its ERP APIs per product on docs.oracle.com. For Fusion Cloud ERP and SCM there are REST API guides, SOAP web service guides, FBDI file imports and BI Publisher reports; for NetSuite there are SuiteTalk REST and SOAP, SuiteQL and RESTlets. Pick the product first, then the style of API, then match your authentication and the exact release version.

How-to

Oracle Work Order Tables: WIP_ENTITIES, WIP_DISCRETE_JOBS and the REST Route

In Oracle E-Business Suite, a discrete work order (job) is stored in WIP_ENTITIES (the identity and name) and WIP_DISCRETE_JOBS (the header detail such as item, quantities, status and dates), with operations in WIP_OPERATIONS, resources in WIP_OPERATION_RESOURCES and components in WIP_REQUIREMENT_OPERATIONS. In Fusion Cloud, do not query tables directly; use the work orders REST resource or a BI report.

How-to

Connect Oracle Integration Cloud (OIC) To Fusion ERP

OIC connects to Fusion ERP primarily through the prebuilt ERP Cloud Adapter, which wraps Fusion's REST and SOAP web services with OAuth-based authentication and pick-list discovery of available business objects and operations, instead of you hand-building every REST call. Use the adapter for standard integrations; drop to a generic REST or SOAP adapter only when the ERP Cloud Adapter does not yet expose the specific service you need.

Error fix

Fix FBDI Import Failures From Interface Table Validation Errors

When a Fusion FBDI import job errors out, the cause is almost always bad data in the interface tables (an invalid value set, a wrong date format, or a missing required column), not the ESS job itself. Open the process's Interface Errors Report or the Correct Import Errors spreadsheet to see the exact rejected rows and reason codes, fix the source data, and resubmit from the interface tables instead of re-running the whole FBDI load.

Error fix

Clear An Oracle Fusion ESS Job Stuck In Blocked Status

A Blocked status on an Oracle Fusion Enterprise Scheduler (ESS) job almost always means an earlier instance of the exact same job is still running or stuck, and the job definition does not allow simultaneous requests. Find and finish, or cancel, the earlier request first; only then does the Blocked request move to Running.

AI for ERP

Fusion Cloud ERP AI: OCI Generative AI Service vs. a Private LLM

How Fusion Cloud ERP AI supports GenAI implementation: OCI Generative AI Service for Fusion-only use cases, a private LLM for sensitive or cross-system data.

AI for ERP

Oracle ERP AI Consulting: What a Partner Should Deliver

Choosing an Oracle JDE partner for AI: what to demand across JD Edwards (Orchestrator, AIS), EBS, NetSuite and Fusion Cloud, plus the buyer questions to ask.

Stuck on Oracle Fusion Cloud Applications?

Talk to engineers who work inside Oracle Fusion Cloud Applications every week, and who build private AI that answers these questions from your own ERP data.

Talk to an ERP engineerBrowse ERP Help
All ERP Help articles

Keep exploring

Free tools

ERP fixes and how-tos

Runs with your ERP

AI on your ERP

Integrations

Comparisons

Software