[sinankeskin]

Greptile Summary

This PR documents initial custom fields for tracking requests. The main changes are:

• Adds shipment and container custom-field guidance to the API reference.
• Adds the nested initial_custom_fields request schema.
• Adds an example with targeted and shipment-wide container values.

Confidence Score: 4/5

The OpenAPI and TypeScript SDK request contracts need to be synchronized before merging.

• The documentation and OpenAPI examples are internally consistent.
• TypeScript SDK callers cannot represent or send the newly documented request field through createTrackingRequest.

docs/openapi.json and the TypeScript SDK request types

Important Files Changed

Filename	Overview
docs/api-docs/api-reference/tracking-requests/create-a-tracking-request.mdx	Adds usage guidance and an example for shipment, targeted-container, and all-container custom fields.
docs/openapi.json	Adds the request schema and example, but the checked-in TypeScript SDK does not expose the new field.

Prompt To Fix All With AI

Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 1
docs/openapi.json:1336
**SDK Contract Omits New Field**

The OpenAPI request now exposes `initial_custom_fields`, but the checked-in TypeScript SDK's `createTrackingRequest` parameters do not accept or forward it. SDK callers following this contract receive an excess-property type error or cannot send the custom fields, so the generated types and public client method need to be updated with this schema change.

_{Reviews (1): Last reviewed commit: "chore: Auto-generate Postman collection ..." | Re-trigger Greptile}

Greptile also left 1 inline comment on this PR.

[linear-code]

DEV-10929

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
api	Ready	Preview, Comment	Jul 17, 2026 5:33pm

[mintlify]

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

Project	Status	Preview	Updated (UTC)
terminal49	🟢 Ready	View Preview	Jul 17, 2026, 4:31 PM

[greptile-apps]

SDK Contract Omits New Field

The OpenAPI request now exposes initial_custom_fields, but the checked-in TypeScript SDK's createTrackingRequest parameters do not accept or forward it. SDK callers following this contract receive an excess-property type error or cannot send the custom fields, so the generated types and public client method need to be updated with this schema change.

Prompt To Fix With AI

This is a comment left during a code review.
Path: docs/openapi.json
Line: 1336

Comment:
**SDK Contract Omits New Field**

The OpenAPI request now exposes `initial_custom_fields`, but the checked-in TypeScript SDK's `createTrackingRequest` parameters do not accept or forward it. SDK callers following this contract receive an excess-property type error or cannot send the custom fields, so the generated types and public client method need to be updated with this schema change.

How can I resolve this? If you propose a fix, please make it concise.

[mintlify]

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

Project	Status	Preview	Updated (UTC)
terminal49	🟡 Building	–	Jul 17, 2026, 4:31 PM

[dodeja]

Status check against main at 558ce0e: this PR is fully covered by #319.

main has:

• initial_custom_fields in docs/openapi.json: the shipment and containers arrays, number targeting, and the rule that an omitted or empty number applies the value to every container.
• The request example.
• The "Setting custom field values before the shipment exists" section in create-a-tracking-request.mdx.

#319 also corrects two details from this PR: container entries are Cargo-scoped, and the custom-field-definition link is updated. I found nothing unique left here. The Postman collection is generated, so it doesn't count as unique work. I'm leaving it open; the owner decides.