"Oracle FSCM REST API: What Transfers From HCM and What Doesn't"

If you've integrated with Oracle Fusion HCM (/hcmRestApi/), the Financials and Supply Chain surface (/fscmRestApi/) is 90% the same API with a different catalog. Here's the 10% that matters, with working examples. Replace acme.fa.us2.oraclecloud.com with your pod; all sample data is anonymized. Same host, different path segment HCM: https://acme.fa.us2.oraclecloud.com/hcmRestApi/resources/11.13.18.05/workers FSCM: https://acme.fa.us2.oraclecloud.com/fscmRestApi/resources/11.13.18.05/invoices Enter fullscreen mode Exit fullscreen mode q, finders, expand, fields, and limit/offset/hasMore pagination all behave identically. Auth is the same too — Basic over TLS for dev, OAuth 2.0 for production. A 403 on an FSCM resource almost always means a missing Financials/SCM duty role, not a wrong URL. Know how filterable a resource is before you call it These numbers come from the real Oracle OpenAPI spec: That last row is the gotcha pattern: some resources are all q fields and no finders, others the reverse. Checking first saves you from writing a filter the endpoint can't serve. q filters that actually work on /invoices Real queryable fields include BusinessUnit, ApprovalStatus, AmountPaid, AccountingDate: GET /fscmRestApi/resources/11.13.18.05/invoices ?q=AmountPaid=0 and BaseAmount>10000 and AccountingDate>'2026-01-01' Enter fullscreen mode Exit fullscreen mode Lowercase and/or, single quotes on strings only, URL-encode exactly once. Prefer finders when they exist GET /fscmRestApi/resources/11.13.18.05/payablesPayments ?finder=PrimaryKey;CheckId=300000001234567 Enter fullscreen mode Exit fullscreen mode /expenses ships FindCCTransactions and friends; /receivablesInvoices has invoiceSearch. Finders map to indexed view criteria on Oracle's side — consistently faster than the equivalent q on large tables. The FSCM-specific 404 Resource names are camelCase and case-sensitive: payablesPayments works, payablespayments is a 404 that looks like a valid path. This one costs people hours. Full guide with expand examples, pagination, and the complete error table: Oracle FSCM REST API: Base URL, Key Endpoints, and Working Examples. I build OPAL, an offline Oracle Fusion API explorer — 59,000+ HCM/FSCM endpoints searchable without internet, with visual q filter and finder builders and a full endpoint reference.