> For the complete documentation index, see [llms.txt](https://docs.partssource.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.partssource.com/webhooks-customer/preview/preparing-your-integration.md).

# Preparing Your Integration

A migration checklist for the upcoming webhooks release

{% hint style="warning" %}
**Preview** — this page describes the upcoming release (early September). Content is subject to change until announced in the changelog. Build against the **Current** variant for today's behavior.
{% endhint %}

1. **Unknown event types:** acknowledge with 2xx and ignore. New events will appear on your subscription only after you opt in, but defensive handling costs nothing.
2. **New optional fields:** parse leniently — additive fields on existing events and endpoints are not treated as breaking changes.
3. **Ordering:** the new events do not change the ordering guarantee — there is none. `tracking.updated` can arrive before `tracking.assigned` after a redelivery; `delivered` can arrive before `shipped`. Key all state transitions on the event content, not arrival order.
4. **Deduplication:** the composite key (`event_type:order_id:line_item_id:occurred_at`) works unchanged for all new events.
5. **Retired events:** `order.line.estimated_ship_date.created` and `.updated` stop being emitted in this release. Migrate consumers to the `customer.shipment.estimated_ship_date.*` pair before the release date.
6. **ORDERS endpoints:** the same release also expands the ORDERS endpoints' line item shape — see [ORDERS Endpoint Enhancements](https://docs.partssource.com/api-customer/preview/orders-endpoint-enhancements) in the Customer API Preview. The new fields are additive; renamed fields keep their current names as deprecated aliases during a transition window.
7. **Changelog:** every change in this document will appear in the changelog before it goes live. Subscribe your team to the documentation changelog page; nothing ships silently.


---

# 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.partssource.com/webhooks-customer/preview/preparing-your-integration.md?ask=<question>&goal=<endgoal>
```

`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.