Staging: carrier-integration-api main at 8eb88c7. Carriers do not see this version yet.
Mock Service API (staging)

Mock Service API (staging)

Staging-only trigger operations that simulate parcel and locker events. For the first steps, read the Testing guide.

Staging only

Base URL: https://api.staging.glsnxt.com/ooh-mock-service/v1. Authenticate with your regular carrier staging API key in the X-API-Key header. You do not need a separate mock-service key.

Request bodies use snake_case field names. A booking uses the platform lockerUid. A trigger request uses the provider-side provider_locker_id. For a test locker the two values can be equal, but this is not always true. Read provider_locker_id from the platform (see the Testing guide, section 2.1).

A 200 response is not a confirmation

The mock answers 200 when it accepts the request, before it sends the event. The message text, for example Last Mile event triggered successfully, has the same meaning. The platform processes the event a few seconds later. If the platform rejects or drops the event, you get no error from the mock. Always check the result in your webhooks or with GET /parcels (Testing guide, section 2.2).

Always send your own carrier name in carrier_name. With a different carrier name, the mock returns 200, but the platform drops the event.