Oracle FSCM REST API: Base URL, Key Endpoints, and Working Examples

Oracle Fusion’s Financials and Supply Chain APIs live under a single REST base path: /fscmRestApi/. If you have worked with the HCM API (/hcmRestApi/), everything transfers — the q parameter, finders, expand, fields, and pagination behave the same way. What changes is the resource catalog: invoices, payments, expenses, receivables, procurement, and inventory instead of workers and assignments.

This guide covers the base URL and versioning, authentication, the endpoints you will actually use, and copy-paste request examples built from the real OpenAPI spec metadata. Replace acme.fa.us2.oraclecloud.com with your pod’s hostname; all sample data is anonymized.

What “FSCM” covers

FSCM is not a separate product — it is the shared REST surface for two Oracle Fusion pillars:

Financials: payables (invoices, payablesPayments), receivables (receivablesInvoices), general ledger (journalBatches), cash management (cashBankAccounts, cashExternalTransactions), expenses (expenses, expenseReports), and joint ventures.
Supply Chain Management: procurement, order management, inventory, product management, and manufacturing resources.

Both are served from the same host as your other Fusion modules — only the path segment differs:

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

11.13.18.05 is the stable REST resource version Oracle has kept for years; you can also use latest, but pinning the version keeps integrations predictable.

Authentication

Same options as every Fusion REST API: Basic Auth over TLS (fine for development and many internal integrations) or OAuth 2.0 with JWT (recommended for production). The user needs the relevant Financials or SCM duty roles — a 403 on an FSCM resource almost always means a missing role, not a wrong URL.

GET https://acme.fa.us2.oraclecloud.com/fscmRestApi/resources/11.13.18.05/invoices?limit=5
Authorization: Basic base64(username:password)
Content-Type: application/json

Key endpoints and what they expose

Numbers below come straight from the Oracle OpenAPI spec (the same data OPAL indexes offline). They matter because they tell you how filterable each resource is before you write a single request.

Resource	Path	Queryable (q) fields	Finders	Child resources
Payables invoices	`/invoices`	88	1	7 (lines, installments, prepayments…)
Expenses	`/expenses`	110	4	8 (distributions, itemization, attendees…)
Payables payments	`/payablesPayments`	82	2	3 (related invoices, DFFs)
Receivables invoices	`/receivablesInvoices`	18	2	8 (lines, distributions, installments…)
Payables interface invoices	`/payablesInterfaceInvoices`	186	0	0
Joint ventures	`/jointVentures`	62	4	—

Browse the full field lists, operators, and finder signatures for all of these in the FSCM section of our API reference — for example invoices, expenses, and payablesPayments.

Filtering with q

The q parameter works identically to HCM. Real queryable fields on /invoices include BusinessUnit, ApprovalStatus, AmountPaid, AccountingDate, and BankAccount:

GET /fscmRestApi/resources/11.13.18.05/invoices
    ?q=BusinessUnit='US1 Business Unit' and ApprovalStatus='REQUIRED'
    &limit=25

Unpaid invoices above a threshold:

GET /fscmRestApi/resources/11.13.18.05/invoices
    ?q=AmountPaid=0 and BaseAmount>10000 and AccountingDate>'2026-01-01'

Expense records for a business unit that still have an attachment:

GET /fscmRestApi/resources/11.13.18.05/expenses
    ?q=BusinessUnit='US1 Business Unit' and AttachmentExists='Y'

Remember to URL-encode the expression in real clients — spaces become %20, quotes %27. If a filter silently returns everything, check you did not send the literal q= string twice (see our q + expand troubleshooting note).

Finders

Finders are Oracle’s predefined, optimized searches. FSCM resources ship useful ones:

/expenses — FindCCTransactions, FindCcTrxnByRequest, FindSavedCCExpenses, PrimaryKey
/payablesPayments — PaidInvoicesFinder, PrimaryKey
/receivablesInvoices — invoiceSearch, PrimaryKey

GET /fscmRestApi/resources/11.13.18.05/payablesPayments
    ?finder=PrimaryKey;CheckId=300000001234567

When a finder exists for your use case, prefer it over an equivalent q expression — finders map to indexed view criteria on Oracle’s side and are consistently faster on large tables.

Expanding child resources

Payables invoices carry seven child resources. Instead of one request per child, expand them inline:

GET /fscmRestApi/resources/11.13.18.05/invoices
    ?q=ApprovalStatus='APPROVED' and AmountPaid=0
    &expand=invoiceLines,invoiceInstallments
    &limit=10

Receivables invoices work the same way with receivablesInvoiceLines and receivablesInvoiceInstallments. Keep expand lists short — each expanded child multiplies payload size, and combining expand=all with a broad filter is the fastest way to hit a timeout.

Pagination

Identical to HCM: limit (default 25), offset, and totalResults=true when you need a count. Responses include hasMore, so loop until it is false:

GET /fscmRestApi/resources/11.13.18.05/invoices?limit=100&offset=200&totalResults=true

Common errors

400 — malformed q expression (unencoded quotes, wrong operator for the field type). The spec’s per-field operator list in the reference pages shows what each field supports.
401 — bad credentials or expired token.
403 — authenticated but missing the Financials/SCM duty role for that resource.
404 with a valid-looking path — usually a typo in the resource name; FSCM resource names are camelCase and case-sensitive (payablesPayments, not payablespayments).

Finding the right FSCM endpoint in the first place

The FSCM spec alone defines 1,300+ endpoint paths, and Oracle’s documentation lists them alphabetically. If you know the field you need but not the resource it lives on, an offline index helps: OPAL bundles the full FSCM catalog searchable by name, parameter, or description, and shows every q field, finder, and child resource before you send a request.

This post is part of our complete Oracle Fusion API guide — pillars, base URLs, authentication, q filters, finders, and common errors in one place.