Endpoint Setup

Once you are inside the webhook portal, your first job is to create an endpoint that YunoJuno can deliver events to.

An endpoint is simply an HTTPS URL that you control.

Before you add the endpoint

Make sure the receiving service is ready to:

• accept POST requests over HTTPS
• return a 2xx response quickly once a message has been accepted
• verify the webhook signature before trusting the payload
• process the same message more than once without creating duplicate side effects

That last point matters because replay and retry are normal webhook behaviors.

Create the endpoint

1. Open the Endpoints area in the portal.
2. Click Add Endpoint.
3. Enter the destination URL.
4. Add a clear name or description so the endpoint is easy to identify later.
5. Configure endpoint authentication if your service requires it. See Securing Your Endpoints for the recommended setup.
6. Save the endpoint.

Secure the endpoint

As part of setup, decide how the receiving service should authenticate requests before you enable live delivery.

The portal supports two practical patterns:

• API headers
• HTTP Basic Auth

We recommend API headers in most cases because they are easier to rotate, easier to route through proxies and load balancers, and avoid embedding credentials directly into the endpoint URL.

Use Securing Your Endpoints to choose the right pattern and implement signature verification alongside it.

Subscribe to event types

After the endpoint exists, choose which events it should receive.

The portal’s Event Catalog shows:

• the event names available to subscribe to
• the shape of each payload
• an example payload for each event type

You can also review the full catalog of currently documented events in the API reference at Webhook Events.

If you do not narrow the selection, the endpoint can receive all available events. That can be useful at the start of an integration, but production endpoints should usually be scoped to the events your system actually handles.

Test before going live

Use the portal’s testing tools to send example events to the endpoint before you rely on live traffic.

This is the fastest way to confirm:

• the URL is reachable
• your authentication settings are correct
• your signature verification works
• your service returns the expected 2xx response