URL Structure

This topic summarizes the URL structures to use for the REST APIs.

For the URL structure to use, see the topic for the REST API:

• Planning and Budgeting REST API URL
• Migration REST API URL
• URL Structure for Security
• URL Structure for Daily Maintenance
• URL Structure for Users, Groups, and Roles
• Data Management REST API URL
• Account Reconciliation REST API URL
• Enterprise Profitability and Cost Management REST API URL
• URL Structure for Financial Consolidation and Close
• Profitability and Cost Management REST API URL
• URL Structure for Tax Reporting

In the description and examples of all REST APIs, this guide uses <BASE-URL>. The <BASE-URL> is the first part of your service URL, before the context. For example, 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.

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.

For details on the URL structure, see Getting Started for Administrators.