Oraclecloud Supplier
0
AI ReadinessNon-Ready (F)0/100
Community OpenAPI document · agent-readyFinanceAccountingbasic9 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Create suppliers in Oracle Fusion Cloud, add their address, site, and business unit assignment, register their bank branch and external bank account, and assign that account as the payment instrument for supplier disbursements.
Use for: I need to onboard a new supplier into Oracle Fusion Payables, Create a supplier site with email as the communication method, Register a bank branch for J.P. Morgan Chase Bank in Oracle Fusion, Add an external savings bank account for a supplier
Not supported: Does not create invoices, run payment batches, issue purchase orders, or post general ledger journals. Use for onboarding Oracle Fusion suppliers and their bank payment instruments only.
The Supplier API onboards suppliers into Oracle Fusion Cloud Financials through the fscmRestApi resources, covering the steps Payables needs before a supplier can be paid. It creates the supplier record with fields such as Supplier, SupplierType, BusinessRelationship, and TaxOrganizationType, then adds a supplier address, a supplier site, and the site's business unit assignment. On the payments side it registers bank branches and external bank accounts, looks up external payees, and assigns a bank account as the supplier's payment instrument for disbursements. This spec targets a test Fusion instance and its child-resource paths are written against fixed supplier and site ids.
Install Jentic One Beta
Connect the Supplier to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Supplier, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Foraclecloud.com%2Foraclecloud" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Foraclecloud.com%2Foraclecloud" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Supplier API.
Create a supplier record with Supplier, SupplierType, BusinessRelationship, and TaxOrganizationType through the suppliers resource
Add a supplier address, a supplier site with its CommunicationMethod and Email, and a site assignment to BillToBU and ClientBU business units
Register a bank branch with BankName, BankBranchName, and BranchNumber through cashBankBranches
Create an external bank account for a supplier with BankAccountName, BankAccountNumber, and AccountType
Look up external payees with the paymentsExternalPayees finder and assign a bank account as a DISBURSEMENTS payment instrument
Use Cases
Patterns agents use Supplier API for, with concrete tasks.
★ Agent-run supplier onboarding
A procurement agent onboards a vendor approved in another system by calling the Oracle Fusion supplier resources through Jentic in sequence: create the supplier, add its address, create a site, and assign the site to the paying business unit. Jentic returns each operation's input schema, so the agent fills fields like BusinessRelationship and BillToBU correctly, and your own Jentic One instance injects the Fusion username and password at call time.
POST /fscmRestApi/resources/latest/suppliers with Supplier 'Acme Pte Ltd', SupplierType 'Supplier', BusinessRelationship 'Spend Authorized', and TaxOrganizationType 'Corporation', then report the created supplier record
Supplier bank account setup for payment runs
Before Payables can disburse funds, the supplier needs a bank account tied to it as a payment instrument. The flow registers the bank branch through cashBankBranches, creates the external bank account through externalBankAccounts, and then posts an instrumentAssignments record with PaymentFlow DISBURSEMENTS and PaymentInstrumentType BANKACCOUNT linking the account to the payee's PaymentPartyId.
POST /fscmRestApi/resources/11.13.18.05/externalBankAccounts with BankAccountName 'Acme SG', BankAccountNumber '8830023556', and AccountType 'SAVINGS', then POST /fscmRestApi/resources/11.13.18.05/instrumentAssignments with Intent 'Supplier', PaymentFlow 'DISBURSEMENTS', PaymentInstrumentType 'BANKACCOUNT', and the new PaymentInstrumentId
Payee and instrument lookups
Finance teams checking why a supplier payment failed need to confirm the payee exists and which instrument it uses. The paymentsExternalPayees operation searches payees with its finder and q parameters, and the instrumentAssignments read operation lists the assignments a finder matches, so an agent can report whether a bank account is attached before a payment run.
GET /fscmRestApi/resources/11.13.18.05/paymentsExternalPayees with a finder for the supplier's party, then GET /fscmRestApi/resources/11.13.18.05/instrumentAssignments with a finder for that payee and report the assigned instrument
Key Endpoints
9 endpoints — the supplier api onboards suppliers into oracle fusion cloud financials through the fscmrestapi resources, covering the steps payables needs before a supplier can be paid.
METHOD
PATH
DESCRIPTION
POST
/fscmRestApi/resources/latest/suppliers
Create a supplier
POST
/fscmRestApi/resources/latest/suppliers/300000004876298/child/sites
Create a supplier site
POST
/fscmRestApi/resources/11.13.18.05/cashBankBranches
Create a bank branch
POST
/fscmRestApi/resources/11.13.18.05/externalBankAccounts
Create an external bank account
GET
/fscmRestApi/resources/11.13.18.05/paymentsExternalPayees
Search external payees
POST
/fscmRestApi/resources/11.13.18.05/instrumentAssignments
Assign a payment instrument
POST
/fscmRestApi/resources/latest/suppliers
Create a supplier
POST
/fscmRestApi/resources/latest/suppliers/300000004876298/child/sites
Create a supplier site
POST
/fscmRestApi/resources/11.13.18.05/cashBankBranches
Create a bank branch
POST
/fscmRestApi/resources/11.13.18.05/externalBankAccounts
Create an external bank account
GET
/fscmRestApi/resources/11.13.18.05/paymentsExternalPayees
Search external payees
POST
/fscmRestApi/resources/11.13.18.05/instrumentAssignments
Assign a payment instrument
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
S
Supplier
- Non-Ready (F)0/100
99
Foundational Compliance75
Developer Experience & Jentic Compatibility33
AI-Readiness & Agent Experience94
Agent Usability10
Security0
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
99
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
95%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
75
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: A-Signals: 4
78%
Example Density
How richly the API is illustrated with examples.
98%
Example Validity
Percentage of examples that conform to their schemas.
25%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
33
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
2%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
29%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
10
Security
Trust, risk posture, and security compliance.
Grade: FSignals: 1
10%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
0
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: FSignals: 1
0%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Oracle Fusion by hand means Basic auth against your pod's host, versioned fscmRestApi resource paths, and chaining supplier, site, bank account, and instrument calls in the right order. Through Jentic you install once, import the Supplier API from the API Directory, store the credentials once, and your agent calls it.
Permission scoping
Each step of supplier onboarding is a separate operation, so a rule can let your agent read payees and instrument assignments while leaving supplier creation and bank account creation out. The target records travel in request bodies or finder queries, so rules bound which operations the agent may call, not which supplier.
Credential isolation
Your Fusion username and password are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create a supplier bank account' or 'assign a payment instrument', and Jentic returns the matching Fusion operation with its input schema so the agent sends the right fields without browsing Oracle's REST reference.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Supplier API through Jentic.
What authentication does the Oracle Fusion Supplier API use?
This Supplier spec declares HTTP Basic authentication: a Fusion username and password sent in the Authorization header. Through Jentic those credentials are stored encrypted by your own Jentic One instance and injected at call time, so they never enter the agent's prompt or logs.
Can I set up a supplier's bank account for payments with this API?
Yes. Register the branch through cashBankBranches if it does not exist, create the account through externalBankAccounts with fields such as BankAccountName, BankAccountNumber, and AccountType, then link it with an instrumentAssignments POST that sets PaymentFlow to DISBURSEMENTS, PaymentInstrumentType to BANKACCOUNT, and the payee's PaymentPartyId.
Why do some paths in this spec contain fixed numeric ids?
The address, site, and site assignment paths are written against one supplier id (300000004876298) and one site id (300000004876565) from a test Fusion instance, rather than as path parameters. To work with a different supplier, the equivalent Oracle Fusion resource paths take that supplier's own id in the same position.
How do I onboard a supplier in Oracle Fusion through Jentic?
Install Jentic One, add the Supplier API from the Jentic API Directory, and store your Fusion username and password once. Your agent searches for 'create a supplier in Oracle Fusion', gets the suppliers create operation with its input schema, and posts the supplier, then continues with the site and bank account operations. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Is there an Oracle Fusion Supplier MCP server?
You don't need an MCP server to give your agent the Oracle Fusion Supplier API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it, discovering operations on demand instead of loading extra tool definitions into its context.
Can I limit what my agent is allowed to do with the Oracle Fusion Supplier API?
Yes. For a lookup-only agent, write a rule that allows just the paymentsExternalPayees and instrumentAssignments read operations: it can check payees and their instruments but cannot create suppliers or bank accounts. Add the create operations only for an onboarding agent, and every call is logged by your own Jentic One instance.
GET STARTED