Encoding Required for Space Character in the Value of Path or Query Parameter in REST APIs

Starting with this monthly update, if there is a space in the value of a parameter that is specified in the URL itself (that is, it is a path or query parameter), this space must be encoded with %20.

Examples:

GET /interop/rest/security/v2/report/roleassignmentreport/user?userlogin=admin1&rolename=Service%20Administrator

GET /interop/rest/security/v2/report/roleassignmentreport/group?groupname=Planning%20Analysts&rolename=Service%20Administrator

The values of payload parameters do not need to be encoded.

No change is required in EPM Automate syntax.

Applies to: Account Reconciliation, Enterprise Data Management, Enterprise Profitability and Cost Management, Financial Consolidation and Close, FreeForm, Narrative Reporting, Planning, Profitability and Cost Management, Tax Reporting

Business Benefit: This change enhances the security of the REST APIs.

Steps to Enable

Review the REST service definition in the REST API guides to leverage (available from the Oracle Help Center > your apps service area of interest > APIs & Schema). If you are new to Oracle's REST services you may want to begin with the Quick Start section.

Tips And Considerations

Use these Implementation Best Practices to ensure success with your REST API projects.

Key Resources

• REST API for Oracle Enterprise Performance Management Cloud
  • REST Resources and Methods
  • About the REST APIs for EPM Cloud
  • EPM Cloud REST API Compatibility
  • Quick Reference Table - REST API Resource View

Access Requirements

• Service Administrators