import BeforeYouBegin from '_core/components/BeforeYouBegin/BeforeYouBegin';

# Destinations in Developer Portal

<BeforeYouBegin />

A destination is where noon sends events — a webhook URL you control, plus which event types it's subscribed to. This guide covers creating, subscribing, and managing destinations in the portal. For the concepts behind Event Notifications (event types, delivery guarantees, retry policy), see [Event Notifications][event-notifications-intro].

## Step 1 — Open Destinations

Go to **Event Notifications → Destinations** in the portal.

- If you haven't created a destination yet, you'll see an empty state with a **Create Destination** button.
- If you already have destinations, you'll see two summary cards — **Total Destinations** and **Total Subscriptions** (the combined count of event types subscribed across all your destinations) — followed by the destination list.

![Destinations page with summary cards and the destination list][event-notifications/destinations-list]

## Step 2 — Create a destination

Click **Create Destination**. The dialog has two steps:

1. **Configuration** — name the destination and pick a **Destination Type**. **HTTPS Webhook** is currently the only supported type.
2. **Miscellaneous** — fields here depend on the destination type. For HTTPS Webhook:
   - **Destination URL** *(required)* — the `https://` endpoint noon will POST events to.
   - **Credentials** *(optional, up to 3 key-value pairs)* — sent with every request so you can authenticate it on your side. As you add pairs, the dialog shows the exact `curl` command noon will send, so you can confirm your endpoint expects the right shape.

![Create Destination dialog, Configuration step][event-notifications/create-destination-configuration]

![Create Destination dialog, Miscellaneous step with a URL and one credential pair filled in][event-notifications/create-destination-miscellaneous]

Click **Create**.

**Success check:** You're returned to the Destinations list and your new destination appears there.

:::info The destination isn't subscribed to anything yet
Creating a destination does **not** ask you to pick event types — it's created with zero subscriptions and won't receive any traffic until you subscribe it. Continue to Step 4 to choose which events it should get.
:::

**If something goes wrong:**
- An invalid or malformed URL is rejected inline before the destination is created — fix it and click **Create** again.
- Each project can have up to 5 destinations — see [Event Notifications][event-notifications-intro] for this and other destination-type details.

## Step 3 — Review and filter your destinations

Each destination in the list shows its name, type and URL, a pill with its subscribed event-type count, an active/inactive toggle, an edit icon, and a chevron to expand it.

- Click a destination (or its chevron) to expand it and see the full table of subscribed events, grouped by namespace.
- **Expand All / Collapse All** toggles every destination at once.
- The **Filter by event type** control above the list narrows it down to only the destinations subscribed to the event types you pick.
- Switching a destination **off** asks you to confirm first, since it stops delivery to that destination immediately; switching it back **on** takes effect right away, no confirmation needed.

![An expanded destination showing its subscribed events grouped by namespace][event-notifications/destination-events-table]

## Step 4 — Subscribe a destination to event types

Click the edit (pencil) icon on a destination to open **Edit Destinations**.

1. **Destination Configuration** — update the name, URL, or credentials. Destination Type can't be changed after creation.
2. **Event Configuration** — browse event types by namespace. Click a namespace to expand it, check individual events, or check the namespace itself to select every event under it at once. Use **Select All** / **Deselect All** for every event type across all namespaces, or the filter to narrow the list while you work. The selected count updates live. Not sure what an event type actually contains? See [Event Types][event-notifications/noon-event-types] for field definitions and example payloads.
3. Click **Save Changes**.

![Edit Destinations page with the Event Configuration section expanded, showing 2 events selected][event-notifications/edit-destination-events]

**Success check:** You're returned to the Destinations list, and the event-type pill on your destination reflects the new count.

**If something goes wrong:**
- Changes aren't saved until you click **Save Changes** — navigating away first discards them.

## Next steps

- [Analytics][developer-portal-event-notifications-analytics] — check delivery performance for your destinations.
- [Logs][developer-portal-event-notifications-logs] — search individual delivery attempts.
- [← Back to Event Notifications overview][developer-portal-event-notifications]