> For the complete documentation index, see [llms.txt](https://docs.evitalrx.in/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.evitalrx.in/api-for-fulfillment-portal/webhooks/overview.md). # Overview Webhooks allow your system to receive **real-time updates** whenever an event occurs in the Fulfillment process. Instead of polling the API, we notify your endpoint with structured event data, enabling seamless integration. ### Webhook Details 1. [Digitization Completed](/api-for-fulfillment-portal/webhooks/digitization-completed.md) - When the order is Digitized at our PaaS Portal then it is triggered. It is used in [**Order With Prescription Flow**](/api-for-fulfillment-portal/orders/place-order.md) & an **optional** Webhook. 2. [Digitization Rejected](/api-for-fulfillment-portal/webhooks/digitization-rejected.md) - When the Prescription Order is cannot be fulfilled this webhook will be triggered. 3. [Order Assigned](/api-for-fulfillment-portal/webhooks/order-assigned.md) - When Order is placed and gets assigned to a pharmacy. This is generally used in Order With Prescription Flow & It is **optional** Webhook. 4. [Order Accepted](/api-for-fulfillment-portal/webhooks/order-accepted.md) - When order get accepted by pharmacist. 5. [Order Rejected](/api-for-webhook-responses/order-rejected.md) - If an order is rejected by the pharmacist or order is cancelled manually then this webhook is called. 6. [Order Re-Assign](/api-for-fulfillment-portal/webhooks/order-reassigned.md) - When a Order gets Rejected by Pharmacy we try to re-assign it to another nearby pharmacy. 7. [Order Shipped](/api-for-fulfillment-portal/webhooks/order-shipped.md) - When order is ready for shipping. * At this stage the delivery is being assigned to our delivery partner and tracking URL is available. But, it might show no delivery assigned as it will be searching for Delivery Rider. 8. [Order Picked Up](/api-for-fulfillment-portal/webhooks/order-picked-up.md) - When order is picked up by delivery rider and details of Delivery rider are available. 9. [Order Delivered](/api-for-fulfillment-portal/webhooks/order-delivered.md) - When Order Gets Delivered to patient. 10. [Order Split](/api-for-fulfillment-portal/webhooks/order-split.md) ⛔- When order gets reassigned this webhook this triggered. ### Webhook Sequence #### Delivery Order Sequence 1. Digitization Completed. *(Only Prescription Order)* 2. Digitization Rejected. *(Only Prescription Order)* 3. Order Assigned. (Optional) 4. Order Accepted. 5. Order Rejected. 6. Order Re-Assign. *(If Order gets Re-assigned)* 7. Order Shipped 8. Order Picked Up 9. Order Delivered #### Pickup Order Sequence 1. Order Accepted. 2. Order Rejected. 3. Order Shipped 4. Order Delivered --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.evitalrx.in/api-for-fulfillment-portal/webhooks/overview.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.