Event hooks are outbound calls from Okta that trigger process flows within your own software systems. They're sent when specific events occur in your org, and they deliver information about the event. Unlike inline hooks, event hooks are asynchronous and don't offer a way to execute the Okta process flow. After sending the call, the Okta process flow continues without waiting for a response from the called service.
To set up an event hook, you need to implement a web service with an internet-accessible endpoint. It's your responsibility to arrange hosting of your code on a system that is external to Okta. Okta defines the REST API contract for the requests that it sends to your custom code, and for the responses your custom code can send back.
There are several resources available to help you with event hooks.
Learn more about Okta Event Hooks.
Learn about Hooks best practices.
Learn about which events are eligible Events API.
For information about the Event Hooks API, see Event Hooks Management API.
For a functional example of an event hook, see Event hook implementation.
For a functional example of an event hook with a filter, see Event hook filtering.