---
title: "Notify an event for the given parcel."
method: POST
path: "/v1/parcels/{parcel_id}/notify"
tags: ["parcels"]
---

# Notify an event for the given parcel.

`POST /v1/parcels/{parcel_id}/notify`

## Request

- Base URL: `https://logistics.api.cabify-sandbox.com`
- URL: `https://logistics.api.cabify-sandbox.com/v1/parcels/{parcel_id}/notify`
- Auth: HTTP bearer

Sends an event notification for the specified parcel. Currently, only the `ready_to_pickup`
event is supported.

This event is typically used in food delivery workflows to signal that an order is prepared
and ready to be collected by a driver.

## Path parameters

- `parcel_id` string, uuid, required

## Request body

- object: Request body for sending an event notification for a parcel.
  - `event` 'ready_to_pickup', required: The event to notify. Currently, only `ready_to_pickup` is supported, which signals that the order is prepared and ready to be collected by a driver.

## Response `202`

Event accepted and queued for processing.

## Other responses

- `400`: Bad request. One or more fields failed validation.
- `403`: This parcel does not belong to your account.
- `404`: No parcel found with the given ID.
- `409`: The parcel has not yet been assigned to a modality, or the assigned modality does not support this event.
- `422`: Unprocessable entity. The request is well-formed but contains semantic errors.
- `429`: Too many requests. This API is rate limited per account and per endpoint. A 429 is an expected condition rather than a failed request: back off and retry it. The limits are not the same for every endpoint and can change, so handle the status instead of hard-coding a rate. See the Limits and reliability guide.
- `500`: An unexpected server error occurred.

---

[API](https://skmtc.dev/cabify/apis/cabify-logistics-api.md) - [All operations](https://skmtc.dev/cabify/apis/cabify-logistics-api/llms.txt) - [OpenAPI document](https://skmtc.dev/cabify/apis/cabify-logistics-api/revisions/dff49457aac9?raw)