Identity as a Service (IDaaS) uses an event callback mechanism to push account and organization changes to your application in real time. When a subscribed event occurs — such as an employee being onboarded or a user updating their mobile number — IDaaS sends an HTTP POST request to your configured endpoint carrying the event data in JWT format.
This is an asynchronous push: IDaaS delivers the event and moves on without waiting for your application to finish processing. Return HTTP 200 immediately after receiving the request, then process the event asynchronously. Waiting to respond until processing is complete is the most common cause of delivery timeouts and unnecessary retries.
For the reverse direction (syncing data from your application to IDaaS), see API operations for application development.