> For the complete documentation index, see [llms.txt](https://docs.shippify.co/developers/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.shippify.co/developers/en/integration-guide/basic-processes/status-update.md).
# Status update
Once you have deliveries created within our system, you can proceed with updating statuses. This process involves keeping the statuses of orders updated in your external platform, so when an event occurs within the Shippify application, it also appears reflected in your system.
For example, when a driver completes a delivery from the app, this change will be reflected in the Shippify dashboard. This process is to ensure that this same status is reflected in the dashboard of your external platform.
To perform this update, we have two methods:
{% hint style="info" %}
For either of the two options you choose, you'll need to link our statuses with yours, so you'll need to learn more about our[ delivery life cycle](/developers/en/integration-guide/basic-processes/status-update/statuses.md).
{% endhint %}
---
# 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.shippify.co/developers/en/integration-guide/basic-processes/status-update.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.