Features
Generic API clients force you to work around Oracle's conventions — the enormous specs, the
q= filter syntax, named Finders, multi-account environments, and production safety.
OPAL is designed from the ground up for this specific workflow.
OPAL bundles the complete Oracle Fusion Cloud OpenAPI specifications — HCM (Human Capital Management), FSCM (Financials and Supply Chain Management), and BPM (Business Process Management) — and indexes them into a local SQLite full-text search database. No cloud request, no login, no waiting for a browser tab to load.
Search returns results in under 200ms across endpoint paths, parameter names, descriptions, and schema field names.
Type workers and see every Workers endpoint across all modules. Type
PersonNumber and find every endpoint that exposes it.
Search results — under 200ms
Q Builder output
Generated expression
q=PersonNumber='E12345' AND ActiveFlag=true AND BusinessUnitName LIKE 'UK%'
Oracle's q= parameter syntax is the standard way to filter server-side
across all HCM and FSCM endpoints. Writing it by hand is error-prone — field names are case-sensitive,
string literals must be quoted, and logical operators follow Oracle-specific conventions.
OPAL's Q Builder lets you select fields from a dropdown populated by the real spec — only fields that
support q= filtering are shown. Pick the operator, enter the value,
and OPAL generates the correct expression. Save it as a named query to reuse across sessions.
Every endpoint you open creates a persistent tab that survives app restarts. Tabs hold your URL, all parameter values, headers, authentication, and the last response — so you return to exactly where you left off, even days later.
The request panel is Oracle-aware. Path parameters, query parameters, headers, and JSON request bodies
are all supported. Use {{variable}} syntax in any field
and OPAL substitutes the value from the active environment at send time.
Request tab
Response · 200 OK · 142ms
{ "items": [ { "PersonNumber": "E12345", ... } ], "count": 1 } Flow execution
Extract PersonId from response
Extract AssignmentId
Use AssignmentId in body
Most Oracle integration work involves chains of API calls: look up a worker, extract their assignment ID, use it in a second request, then post a result. Without tooling, this means copy-pasting values between tabs, repeating it per environment, and rebuilding it from scratch next time.
OPAL Flows let you group request tabs into an ordered sequence. Define extraction rules that pull values
from each response — a field path, a header, a status code — and bind them into any later step using
the same {{variable}} syntax. Runs execute in order, stop on the
first failure, and display inline results per step. Save the Flow and run it against any environment.
Oracle consultants regularly work across multiple clients, each with their own dev, test, and production environments — and each with different credentials. OPAL's workspace model is built for this.
Each workspace is a self-contained client engagement. Within it, environments hold the base URL, variables, and one or more named accounts. Switching environment updates every tab instantly — no rebuilding requests. Credentials are encrypted with AES-256-GCM and never leave your machine.
Environment switcher
https://acme.fa.us2.oraclecloud.com
https://acme-test.fa.us2.oraclecloud.com
https://acme-dev.fa.us2.oraclecloud.com
OPAL is a native desktop application. Everything runs locally on your machine — there is no OPAL cloud service involved in any API call you make. Your Oracle credentials, request history, saved flows, and workspace configuration stay on your machine.
There is no telemetry, no usage tracking, and no required OPAL account. The app can be used indefinitely without an internet connection after download. Licenses are validated locally — activation does not require contacting an OPAL server.
Free is a complete offline tool. Pro adds live requests and flows.
No account. No time limit.
One-time payment. All future updates.