Webhook
An HTTP request a third-party service sends to your application when an event happens. The agent uses webhooks to learn about state changes (a payment landed, a meeting moved, a message arrived) without polling.
Why it matters
Polling for state is wasteful and slow. Webhooks are the right pattern for real-time event-driven systems. The agent's "your invoice was just paid" notification fires from a Stripe webhook within milliseconds of the payment landing.
The operational difficulty is webhook security: validating that the webhook actually came from the claimed sender (not an attacker spoofing). Each provider has its own signing scheme; the verification has to be implemented per provider and tested.
How Ajeris handles this
Webhooks for all integrated services are handled by the gateway. Signature verification is per-provider. Verified webhooks are forwarded to the relevant per-user agent. Failed-verification webhooks are logged and dropped. The webhook-handling layer is one of the security guards: production webhook endpoints do not accept unsigned requests.
