Staging: carrier-integration-api main at 8eb88c7. Carriers do not see this version yet.
Carrier webhook endpoints

Locker Events

Serverhttps://carrier.example.com/ooh

This webhook endpoint is designed to push events about locker updates.

  • New Locker: An event will be pushed when a new Locker is created.
  • Locker status: An event is pushed when the locker status changes (enabled/disabled).

Webhook for locker updates

POST
https://carrier.example.com/ooh
/locker-updates

Webhook to push locker updates to any URL provided by the carrier. This endpoint allows carriers to receive real-time updates about lockers.

Webhook for locker updates › Request Body

The locker data that carrier-gateway sends when a locker of the carrier is created or changes. carrier-gateway omits an optional field when it has no value; it never sends `null`.
uid
​string · required

The internal unique identifier assigned to the locker.

​webhook_locker_carrier · required

The details of the locker on the Carrier's system.

​webhook_locker_provider · required

The details of the locker on the Provider's system.

​webhook_location · required

Details about the geographical location of the locker.

​features · required

Features available in the locker.

​metadata[] · required

Additional metadata associated with the locker.

​compartment[] · required

A list of different compartment types available in the locker.

eventTimestamp
​string · date-time · required

The timestamp of the locker status update.

​opening_hours

Locker availability schedule.

Conditional constraints (enforced server-side, not by the generated client):

  • If accessMode is SCHEDULED, weeklySchedule MUST be provided and non-empty.
  • If accessMode is ALWAYS, weeklySchedule MUST be omitted.

The owner of the locker. Absent when the platform has no owner for the locker.

Webhook for locker updates › Responses

Return a 200 status to indicate that the data was received successfully.

No data returned