API Endpoint Flows are Flows that can be triggered from an outside source. Unlike Flows that start with events associated with an application, these Flows can be triggered at any time, so long as the client is hitting the appropriate endpoint with the appropriate security setting.
The client calling the endpoint causes the Flow to execute and the client receives back the output of that execution of the Flow.
You can expose this API endpoint in two ways.
- Exposed as a Webhook
- A Flow exposed at this security level will only be able to be accessed if the client making an invoke/resume/retry request is passing along the proper client token along with the proper invoke URL (which includes a Flow alias). For more information about the client token, see “What’s a client token?” below. For more information about the Flow alias, see “What’s an alias?” below.
- Exposed as a Public Service
- A Flow exposed at this security level will be available to anyone with the invoke URL. This invoke URL is built off of the Flow alias. For more information about the Flow alias, see “What’s an alias?” below.
You change how you want to expose an API endpoint from the API Endpoint Settings dialog.
Once you’ve decided how you want your API Endpoint to be properly exposed, you may then invoke the Flow. For more information on invoking the Flow, see “How to invoke a Flow” below.