URL Structure
This topic summarizes the URL structures to use for the REST APIs.
In the description and examples of all REST APIs, this guide uses:
Table 1-16 REST API URL Placeholders
| Placeholder | Description | Example |
|---|---|---|
<BASE-URL> |
The first part of your service URL, before the context. This placeholder is used throughout this guide in REST API descriptions and examples. | If your service URL is
https://epm-acme.epm.us-phoenix-1.ocs.oraclecloud.com/epmcloud,
your <BASE-URL> is
https://epm-acme.epm.us-phoenix-1.ocs.oraclecloud.com.
Similarly, if your service URL is
https://epm2-acme.epm.us6.oraclecloud.com/epmcloud,
your <BASE-URL> is
https://epm2-acme.epm.us6.oraclecloud.com.
|
api_version |
The version of the REST API | v1, v2,
v3 |
path |
Identifies the REST resource being accessed. | applications, jobs, migration |
Note:
Oracle Fusion Cloud Enterprise Performance Management does not authorize or
support the use of any REST API endpoint not specified in this document. For
example, <BASE-URL> such as
https://epmacme.epm.us-phoenix-1.ocs.oraclecloud.com by
itself will fail.
Similarly, Cloud EPM does not
support the use of REST APIs with the path token
"/internal/" in the URL.
Table 1-17 REST Endpoints - URL Structure
| API Category | Context path | URL Pattern |
|---|---|---|
| Account Reconciliation | armARCS |
|
| Data Integration and Data Management | aif |
|
| Enterprise Journal | HyperionPlanning |
|
| Enterprise Profitability and Cost Management | HyperionPlanning |
|
| Financial Consolidation and Close | HyperionPlanning |
|
| Maintenance Operations | interop |
|
| Users, Groups, Roles, and Access Reports | ||
| Migration | ||
| Security and Access Control | ||
| Usage Simulation | ||
| Planning | HyperionPlanning |
|
| Profitability and Cost Management | epm |
|
| Supplemental Data Manager | HyperionPlanning |
|
| Tax Reporting | HyperionPlanning |
|