1. Developing Applications with Oracle Visual Builder in Oracle Integration 3
  2. Connect Applications to Data
  3. Work With Business Objects
  4. Work with Endpoints to Access Business Objects
  5. Access a Business Object's Resource APIs and Endpoints

Access a Business Object's Resource APIs and Endpoints

For each business object, the Endpoints tab displays information about the endpoints you can call in code.


Description of bo-endpoints-tab.png follows
Description of the illustration bo-endpoints-tab.png

Resource APIs

The Resource APIs node displays the URLs you can use to retrieve business object metadata and data in the Development, Staging, and Live databases.
  • Use the Metadata URLs to retrieve metadata about the business object using its /describe endpoint.
  • Use the Data URLs to modify business object data through CRUD operations.

It's important to use the correct URLs for each phase of your application: Development, Staging, or Live. Development URLs are meant to be used only during your app's development phase and typically take this format:

https://{host-name}/ic/builder/design/{app-name}/{app-version}/

This URL is a pointer to your app's design-time version (as indicated by /ic/builder/design/ in the path) and is simply a preview of your app. It is not meant to allow access to your app from other apps or tools. For example, you might copy the development metadata URL and use it with REST API tools similar to Postman to test the metadata URL during development.

When your app is staged, the URL changes to https://{host-name}/ic/builder/rt/{app-name}/{app-version}/, where /ic/builder/rt/ indicates the runtime version of your app. This URL points to your staged application and can be used from other apps or tools.

When your app is published, Visual Builder generates a permanent URL for your application, something like https://{host-name}/ic/builder/rt/{app-name}/live/, where live replaces {app-version} to indicate that the app is now live.

Resource Cache Control

The Resource Cache Control node displays the caching strategy used to store the business object's data. See Control Data Caching for Business Objects.

Endpoints

The Endpoints node displays the business object's endpoints in tabular format. The display includes the HTTP method, the endpoint URI, an endpoint name that you can use in code, and a description of the endpoint. A filter field at the top of the page allows you to view a subset of the endpoints.

For each business object, five default endpoints are created:

  • Two GET endpoints, to retrieve one or all business object instances
  • A POST endpoint, to create a business object instance
  • A PATCH endpoint, to update a business object instance
  • A DELETE endpoint, to delete a business object instance

If the business object refers to other business objects, endpoints that enable you to retrieve, create, delete, and update those business objects are also provided. You can control the endpoints exposed for each business object by adding or removing them in a resource editor (see Add or Remove Exposed Endpoints).

You can click an endpoint in the list to view the endpoint’s details, for example, details about the endpoint’s settings and the headers sent in the request. The details are displayed in read-only mode, but you can use the Test tab to see the response to requests sent with parameter values that you supply.
Description of bo-endpoints-details.png follows
Description of the illustration bo-endpoints-details.png