# Partner Webhooks
> Source: /api-reference/partner/webhooks
> Outbound webhooks for partner integrations — planned, not available today
> Status: PREVIEW
> Note: Planned, not available. There are no outbound partner webhooks on api main today; poll the Action Center feeds instead.

<Warning>
  **Journey does not send outbound partner webhooks today.** There is no
  subscription endpoint, no signing secret, and no event catalogue. The only
  webhook endpoints in the platform are *inbound* ones Journey consumes from
  Entri, LiteAPI and Stripe. If an integration guide or proposal mentions
  partner webhooks, treat it as planned work.
</Warning>

This page exists so the gap is explicit: partners regularly ask for push
delivery, and the honest answer is "poll, for now".

## What to do instead [#what-to-do-instead]

Poll the two Action Center feeds. They are the authoritative source for work
waiting at the front desk.

| Feed | Endpoint | Scope | Notes |
|---|---|---|---|
| Arrivals | `GET /partner/arrivals` | `partner:arrivals:read` | Benefits the engine says arriving members are owed, from −7 to +60 days. Refreshed every 6 hours for arrivals 3 days out. |
| Fulfillments | `GET /partner/fulfillments/pending` | `partner:fulfillments:read` | Offers members have claimed and that are waiting on the desk. |

A poll every 1–5 minutes is plenty for both; neither feed changes faster than
the underlying guest behaviour.

<Note>
  Acknowledging an arrival (`POST /partner/arrivals/{taskId}/ack`) records that
  someone *saw* the task. It does not record delivery. Only the fulfillment
  actions (`approve`, `reject`, `fulfill`) write a redemption record.
</Note>

## There is also no streaming API [#there-is-also-no-streaming-api]

No SSE and no WebSocket surface is exposed to partners, and no third-party
webhook subscription exists on HXP either.

## What is planned [#what-is-planned]

Outbound partner webhooks are on the roadmap but unscheduled. When they ship,
expect them to cover the same two feeds first (arrival task created,
fulfillment claimed) with HMAC-signed delivery and replay. This page will be
updated with the event catalogue, signature verification and retry policy at
that point.

If push delivery is blocking an integration, raise it with your Journey contact
so it can be prioritised rather than worked around.