Webhooks

YunoJuno webhooks let your systems react to platform events as they happen.

Instead of polling the API to discover that something changed, you register an endpoint and YunoJuno pushes event notifications to you. This is the recommended way to keep downstream systems in sync with contract activity, directory lifecycle milestones, spend requisition changes, and other operational events.

How the model works

At a high level, the flow is:

  1. YunoJuno emits an event.
  2. The event is delivered to one or more webhook endpoints you have configured.
  3. Your endpoint verifies the request, processes it, and returns a 2xx response.
  4. If delivery fails, the webhook portal retries automatically and gives you tools to inspect and recover messages later.

The webhook portal

YunoJuno provides a webhook portal for your integration users.

You use it to:

  • add and manage webhook endpoints
  • subscribe endpoints to the event types you care about
  • inspect payloads and delivery attempts
  • replay failed or missed messages
  • recover after downtime or misconfiguration

Read this guide in order

  • Portal Login: how access is granted and how users sign in
  • Endpoint Setup: how to create an endpoint and subscribe it to events
  • Monitoring, Debugging & Recovery: how to inspect deliveries, understand retries, and recover from failures
  • Securing Your Endpoints: how to protect the endpoint itself and verify signed requests

Event schemas

For the exact event payloads and examples, use the API reference:

The portal’s Event Catalog is the quickest place to browse available event types before wiring an endpoint. The API reference remains the canonical contract for payload structure.