Integrations

Stop polling. Keep the failed handoff visible

Tell each downstream system only what it needs to know, then keep the delivery record when that system is unavailable. Cybership connects endpoint scope, payload contract, attempts, retry, recovery, and signing-secret rollout without making warehouse work wait on the receiver.

Get a free sandboxFollow one delivery

Give one receiver the smallest useful event surface

Northline's ERP subscribes to order-created, order-updated, label-created, and warehouse-complete return events. The Create Webhook surface keeps its HTTPS URL, contact, active state, and exact event selections together so the team can review what leaves Cybership.

When an order changes, its registered payload contract is checked, the exact `orders/updated` subscription selects this endpoint, and the handoff receives a stable event identity. The originating warehouse action continues without waiting for the ERP response.

Create Webhook

One receiving endpoint with its own event scope

Active
Endpoint URL
https://ops.northline.example/webhooks/cybership
Contact Email
integrations@northline.example

Creation accepts HTTPS only. The endpoint URL cannot be changed by the update contract after it is created.

Event subscriptions

4 selected · 93 available

orders/created

Exact event

orders/updated

Exact event

shipping-labels/created

Exact event

returns/warehouse_complete

Exact event

Select All Events for the full registry, or choose the exact events this receiver needs. At least one subscription is required.

From warehouse event to receiver

The registered event contract, selected subscription, and endpoint-specific delivery identity travel together.

Operational event

orders/updated

The order payload matches its registered event contract.

Exact subscription

orders/updated

The selected event sends this update to Northline's ERP endpoint.

Queued handoff

ERP delivery

The receiver gets its own attempt history while warehouse work continues.

Selected payload fields

orders/updated

The complete order is validated; this compact view keeps the relevant fields readable.

{
  "id": "ord_01JNX57N8Q7JDMR4XA6T0C2KYP",
  "order_number": "#NFO-10482",
  "status": "OPEN",
  "fulfillment_status": "FULFILLED",
  "payment_status": "PAID",
  "core_line_item_count": 5,
  "unique_core_line_item_count": 3
}

Delivery envelope

Generated identity, version, timestamp, and attempt context.

x-cybr-event-id
b6f8954a-4a1d-4a97-8bc3-03e26c79201f
x-cybr-event-type
orders/updated
x-cybr-timestamp
1775563458
x-cybr-api-version
v1
x-cybr-delivery-attempt
1

Endpoint idempotency key

b6f8954a-4a1d-4a97-8bc3-03e26c79201f-ep_01JNX4ZR3NK9TQ7W1M8CD6P5VA

The warehouse request does not wait for the receiver. A failed receiver remains visible in delivery logs without rolling back the originating warehouse operation.

Inspect the failure without losing what already worked

Three deliveries succeeded while one return-complete handoff reached four attempts and a 503 response during the ERP maintenance window. The log keeps event, status, response, attempts, time, and the latest error on the same endpoint.

Retry is scoped to the selected delivery and endpoint. Cybership records that another attempt was requested, then sends the operator back to the delivery log for the eventual receiver response instead of claiming immediate success.

Delivery logs

Successes stay visible while one failed handoff is inspected.

4 deliveries
Webhook delivery attempts for the selected Northline endpoint
EventStatusResponseAttemptsDelivered

orders/updated

msg_01JNX5B3GWV8B7KJ2E9Q6FRCZT

Success
202112:04:18 UTC

shipping-labels/created

msg_01JNX58TK7QAC4H2V6W0B9PYMF

Success
204112:01:44 UTC

returns/warehouse_complete

msg_01JNX51GF2SE8R6WMQ4B9V3KTY

Failed
503411:58:09 UTC

orders/created

msg_01JNX4Y2P6NRB7K3V0QF8D5MCA

Success
200211:52:31 UTC

Delivery Details

msg_01JNX51GF2SE8R6WMQ4B9V3KTY

Failed
Event ID
2f5f6b65-a2ca-418a-b95b-c9651ba6587d
Event type
returns/warehouse_complete
Attempts
4
Response status
503
Delivered at
11:58:09 UTC

Latest error

503 Service Unavailable — receiving ERP maintenance window

Retry failed delivery

Selected endpoint

Endpoint

https://ops.northline.example/webhooks/cybership

Event

returns/warehouse_complete

Current attempts

4

Retry requested

Webhook delivery retry requested successfully. Return to the delivery log for the next attempt and its eventual receiver response.

msg_01JNX51GF2SE8R6WMQ4B9V3KTY

Recover deliberately—and rotate without an instant cutover

An unhealthy receiver moves from failed deliveries to an Inactive endpoint instead of continuing to accept normal sends. Once the ERP is healthy, Activate retries the endpoint's failed or cancelled delivery and reports recovery separately from the eventual Active state.

Secret rotation reveals the replacement and keeps the previous secret valid for five minutes. That overlap gives the team time to deploy and verify the receiver before only the new signing secret remains.

Active

Events are eligible for delivery

Failure

Delivery attempts did not reach the receiver

Inactive

Normal delivery pauses for this endpoint

Recovery

Activate retries failed or cancelled deliveries

Active

At least one retried delivery returned HTTP 2xx

Webhooks

Northline Supply · one receiver needs attention

1 endpoint
URLStatusEventsLatest Delivery

https://ops.northline.example/webhooks/cybership

Inactive
4 events
Failed
11:58:09 UTC

Receiver is healthy again

Use the endpoint action to begin recovery.

Recovery requested

The endpoint is not labeled Active prematurely.

Failed or cancelled deliveries retried

1

Retried 1 failed/cancelled delivery. Endpoint will reactivate after at least one successful retried delivery.

If the receiver remains unhealthy, the operator gets an explicit recovery error and can retry after the endpoint returns HTTP 2xx.

Update the receiver's trust without dropping the handoff

Once delivery health is restored, rotate the signing secret through a short overlap that the receiving team can deploy and verify.

New Webhook Secret

Copy the replacement before closing the result.

Rotated

Replacement secret

••••••••••••d8f1

The previous secret remains valid for 5 minutes. Update and verify the receiver during that overlap.

Rotation window

One deployable handoff instead of an instant cutover.

  1. 1
    00:00

    New secret issued

    Copy the replacement into the receiver

  2. 2
    00:00–05:00

    Both secrets accepted

    Verify the deployment without a delivery gap

  3. 3
    05:00

    Previous secret expires

    Only the replacement remains valid

The integration surface is explicit before the first request leaves Cybership.

The shared event registry defines what can be selected, each endpoint owns its subscription scope, and secret rotation gives the receiver a deliberate deployment window.

registered event types
93Each maps to a shared payload contract before outbound delivery.
event namespaces
29Orders, inventory, returns, shipping, billing, and more.
selection modes in Create Webhook
2Choose All Events or check the exact registered events this receiver needs.
rotation overlap
5 minThe previous secret expires after the receiver can be updated.

Trusted by 3PLs and brands

2FLYcoAmmoSquaredAxion FulfillmentIndustry Thread Worksadrafül labs

See it in your operation

Bring us the handoff your team still verifies by polling

Show us the event source, destination, payload contract, failure policy, and recovery expectations. We’ll map the smallest subscription surface, delivery evidence, retry path, endpoint recovery, and signing-secret rollout against your downstream system.

Get a free sandboxBook a demo

No sales call is required to get sandbox access.

Continue exploring

Related workflows

View all features