> 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/customer-webhooks.md).

# Customer Webhooks

Order, shipment, approval, and return events for customer integrations

{% hint style="info" %}
This page describes the current production release. Upcoming changes are documented in the **Preview** variant of this section.
{% endhint %}

PartsSource pushes customer events — order lifecycle, approvals, shipments, backorders, and returns — to your endpoint as they happen. This section documents **what** those events are. **How** webhooks work — building a handler, verifying signatures, delivery semantics and limits, testing, troubleshooting — is covered once for all audiences in the [Webhooks guides](https://docs.partssource.com/webhooks).

## In this section

| Page                                                         | What it covers                                                                  |
| ------------------------------------------------------------ | ------------------------------------------------------------------------------- |
| [Event Catalog](/webhooks-customer/event-catalog.md)         | Every customer event type, the delivery envelope schema, and example deliveries |
| [Payload Reference](/webhooks-customer/payload-reference.md) | Field tables and example payloads for every event                               |

## Getting started

Webhook configuration is managed by the PartsSource integration team: you provide an HTTPS endpoint URL (TLS required) and choose which events you want; you receive a **signing secret** to verify deliveries. Then build your handler with the [Quickstart](https://docs.partssource.com/webhooks/quickstart).

## Deprecation policy

Payload and event changes are announced in the changelog at least 90 days before a breaking release.

| Deprecated                               | Replacement                                     | Sunset              |
| ---------------------------------------- | ----------------------------------------------- | ------------------- |
| `order.line.estimated_ship_date.created` | `customer.shipment.estimated_ship_date.created` | announced + 90 days |
| `order.line.estimated_ship_date.updated` | `customer.shipment.estimated_ship_date.updated` | announced + 90 days |

## REST webhooks vs. CMMS event messaging

If your integration receives events at a URL you registered with the PartsSource integration team and verifies an `X-PS-Signature` header, you are using REST webhooks — this section. If your CMMS receives order updates through api.partsfinder.com, that is CMMS event messaging, documented in the CMMS integration guide.


---

# 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/customer-webhooks.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.