Developer ToolsFree generatorPDF, Excel, Word exportOracle Fusion Cloud SCM

Oracle Fusion REST API URL Builder

Oracle Fusion Cloud applications expose REST resources under a predictable URL pattern. This builder assembles the host, version, resource and query parameters, so you can test calls quickly and share a clean example with your team.

Fill in

Fusion host

Host name of your Fusion Applications environment, without https://.

REST API version

Use the version shown in the REST API documentation for your update.

Resource

Filter (q parameter)

Attribute filters, for example Attr=Value;Attr2 LIKE 'AB%'. Check attribute names in the resource describe.

Fields to return

Comma separated attribute names.

Page size (limit)

Order by

Integration user

Generated code

Download:

Request URL

GET https://your-pod.fa.us2.oraclecloud.com/fscmRestApi/resources/11.13.18.05/workOrders?q=WorkOrderStatusCode=ORA_RELEASED&fields=WorkOrderNumber,WorkOrderStatusCode,ItemNumber&limit=25&offset=0&orderBy=WorkOrderNumber:asc&onlyData=true&totalResults=true

curl command

curl -u "integration.user" \
  -H "Accept: application/json" \
  "https://your-pod.fa.us2.oraclecloud.com/fscmRestApi/resources/11.13.18.05/workOrders?q=WorkOrderStatusCode=ORA_RELEASED&fields=WorkOrderNumber,WorkOrderStatusCode,ItemNumber&limit=25&offset=0&orderBy=WorkOrderNumber:asc&onlyData=true&totalResults=true"

GET https://your-pod.fa.us2.oraclecloud.com/fscmRestApi/resources/11.13.18.05/workOrders?q=WorkOrderStatusCode=ORA_RELEASED&fields=WorkOrderNumber,WorkOrderStatusCode,ItemNumber&limit=25&offset=25&orderBy=WorkOrderNumber:asc&onlyData=true

# Keep requesting with offset increased by limit while the response has hasMore = true.

Single record by key

GET https://your-pod.fa.us2.oraclecloud.com/fscmRestApi/resources/11.13.18.05/workOrders/<resource key>?onlyData=true

# The key is the value shown in the self link of a collection response, not always the visible number.

Resource names, attribute names, status code values and the latest REST version vary by release and by which feature is enabled. Always confirm in the REST API for Oracle Fusion Cloud SCM guide for your update, and encode special characters in the filter. Use OAuth or a dedicated integration user with minimal roles, and never place passwords in shared scripts.

Read-only agents on Fusion data

Optional: talk through how to expose Fusion data to an internal assistant safely, with queries shown and writes approved.

Optional. The tool and every export work without this. No spam.

How to use the builder

Enter your Fusion host, the REST version from your documentation and pick a resource. Add a q filter, the fields you want back and a page size. The tool outputs a GET URL, a curl command, the next page call and the single record pattern. Paste the curl command in a terminal, or copy the URL into a REST client such as Postman. Replace the sample filter with attribute names from the resource describe in your own environment.

Anatomy of a Fusion REST URL

SCM resources live under fscmRestApi/resources followed by a version and the resource name. Query parameters are standard across Oracle REST: q for filters, fields to trim the payload, limit and offset for paging, orderBy for sorting, expand to include child collections, and onlyData to drop link metadata. totalResults adds a count, at some cost on big collections, so use it deliberately.

q: filter expression on resource attributes
fields: comma separated attributes to return
limit and offset: paging, check hasMore
onlyData: remove link metadata from responses

Common mistakes

People copy status values from the user interface and wonder why the filter returns nothing: the API often expects an internal code such as one with an ORA_ prefix. Others forget to page, read only the first set of rows and conclude data is missing. Using a dedicated integration user with narrow roles, rather than a personal login, also avoids surprises when the person leaves. Finally, do not hard code the version across scripts; keep it in configuration.

Testing and security

Try new calls in a test pod first. Check rate and size behavior with realistic limits. Keep credentials out of source control, prefer OAuth or token based access for production integrations and assign only the data and function roles the integration needs. Log the full URL, but never the secret.

Frequently Asked Questions

What is the base path for Oracle Fusion SCM REST APIs?

SCM resources are generally served under /fscmRestApi/resources/ followed by a version number and the resource name. Other pillars such as HCM and financials use their own base paths, so check the guide for the application area.

How do I page through large results?

Use limit for the page size and offset for the starting row, then repeat while the response reports hasMore as true. Keep page sizes moderate and sort by a stable attribute so records are not skipped or repeated between pages.

Why does my q filter return no rows?

Usually an attribute name is wrong, the value is a display label rather than the internal code, or special characters are not encoded. Test the filter with a simpler condition and compare to a record fetched by key.

Can I use this for write calls?

The builder produces read requests. Writes use POST, PATCH or action endpoints with JSON bodies and need careful testing and approvals. Follow the resource documentation and test in a non-production pod first.

If you are building integrations or agents on top of Fusion data, Netray can help design them with read-only defaults and human approval for writes. The URL builder is free to use as it is.

Talk to an Expert Explore More Free Tools

Related Tools

Oracle

More Developer Tools tools

See all

Back to All Tools