[mintlify]

Summary

Explains which customer ID integrations should store and how to match customers on shipments and webhook payloads.

Changes

• Added a "Match customers in API responses and webhooks" section to the Add a Customer guide.
• Explains that the party ID differs from the account ID in relationships.customer, and that relationships.customer is null for parties created via POST /v2/parties.
• Explains how to match customers by party ID through GET /v2/shipments/{id}/party_roles and filter[customer_id].

Context

Several recent assistant conversations asked which customer ID appears in webhooks and which one to store. Every statement in the new section matches the OpenAPI spec and the existing guide.

Not resolved: the Aug 10, 2026 changelog says customers without a linked account are exposed under their party ID. The API reference says relationships.customer is null in that case. Engineering should confirm which behavior is current.

---

^{Need help on this PR? Tag @codesmith-bot with what you need.}

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated
terminal49	🟢 Ready	View Preview	Oct 26, 2026, 4:11 PM

[greptile-apps]

PR author is in the excluded authors list.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
api	Ready	Preview	Oct 26, 2026 4:10pm UTC

[github-actions]

Shadow risk calibration

Signal	Result	Authority
Path classifier	risk:low	Deterministic advisory policy
heuristic fallback	risk-shadow:high	Shadow only

Calibration result: disagreement (low vs high).

Shadow risk never blocks or enables merge. Keep it in observation mode until roughly 50 pull requests have human-reviewed labels, then calibrate before considering any policy use.

[SylvainGravejat]

(Analysis done with Claude)

Checked against tnt-api: relationships.customer is the customer party's linked account and null without one (shipment_serializer.rb, tracking_request_serializer.rb), so the API reference is right and the open question about the Aug 10 changelog resolves to null. filter[customer_id] accepts both IDs, and the party-roles endpoint includes the party.

Two small additions to consider:

• On a shipment shared with you by another account, relationships.customer is omitted entirely, so its absence doesn't mean "no customer".
• Filtering by an account ID also matches that account's own shipments that have no customer role (the creator fallback documented in List filters).