Viewing Endpoints

An API is exposed using an endpoint. An endpoint is the access point of a resource, which a service exposes and a client invokes. The endpoint uses the operations to provide access to the resource. The endpoint is represented by a path within the resource. It resides at a location specified by the URL of the resource.

Note the following when viewing endpoints:

  • Each trigger generates one endpoint regardless of how many paths are implemented as part of the trigger. So, if there are multiple triggers in an app, you get multiple endpoints.
  • As long as there are two or more endpoints in an app, the endpoints are named with the same name as the trigger they represent. If an app has only one trigger, its endpoint is not named. Instead you see the URL for the endpoint.
  • When you create a flow starting with a specification (Swagger specification or GraphQL specification), you get a single trigger and hence only one endpoint.
  • An app can have one or more GraphQL and REST triggers or a combination of both. In such apps, each trigger has its own endpoint.
  • If you import a legacy app, the triggers get consolidated into one trigger, resulting in one endpoint.

After you successfully push an app, you can view its endpoint in the Endpoints tab on the app details page. See the Using TIBCO Cloud™ Integration > Managing App Endpoints > Viewing Endpoints topic for more details.

Note: If you are using a REST trigger in your app:
  • The endpoint URL contains the app name only if the app has one trigger.
  • The endpoint URL contains the app name and trigger name for more than one trigger.
  • If you add a REST trigger to an existing app, you must reconfigure the client app.