feat: add gmc ordertracking (order tracking signals) - #109
Merged
Conversation
Add the Order Tracking sub-API (ordertracking/v1, accounts.orderTrackingSignals) — the last remaining GA Merchant API sub-API, completing the stable v1 surface. The sub-API is write-only: `gmc ordertracking create --file <signal.json>` (or stdin) posts an OrderTrackingSignal so Google can show accurate delivery estimates. There is no get/list/update/delete — a signal is immutable once created. - api: OrderTrackingService + typed OrderTrackingSignal / ShippingInfo / LineItemDetails / ShipmentLineItemMapping shapes; new "ordertracking" sub-API and rate-limit bucket. - cli: `ordertracking create` — reads the signal from --file/stdin, validates the required fields (orderId, shippingInfo, lineItems) offline by shape, strips the output-only orderTrackingSignalId, and supports --merchant-id. - auth: map the sub-API to the content scope. - docs: new reference page; roadmap/index updated to 12 GA sub-APIs. cli 1.0.16, api 0.9.21, auth 0.7.3.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds
gmc ordertracking— the Order Tracking sub-API (ordertracking/v1,accounts.orderTrackingSignals). This was the last remaining GA (v1) Merchant API sub-API, so the stable v1 surface is now fully covered (12 sub-APIs).Order tracking signals report completed shipments so Google can show accurate delivery estimates. The sub-API is write-only — there is no get/list/update/delete, and a signal is immutable once created.
Changes
OrderTrackingService+ typedOrderTrackingSignal/ShippingInfo/LineItemDetails/ShipmentLineItemMappingshapes; registers theordertrackingsub-API (union + rate-limit bucket).ordertracking create: reads the signal from--file/stdin, validates the required fields (orderId, non-emptyshippingInfo, non-emptylineItems) offline by shape (an object-instead-of-array or a blank id fails fast, not as an opaque 400), strips the output-onlyorderTrackingSignalId, and supports--merchant-id.ordertrackingto the content scope (mirrors every sibling sub-API).reviews/productstudio/youtuberemain pre-GA and are deferred until they graduate tov1.Contract accuracy
The wire shape was verified against the
google/shopping/merchant/ordertracking/v1proto:POST /ordertracking/v1/{parent=accounts/*}/orderTrackingSignalswith the signal as the request body — nodataSource(unlike products/promotions). The API test asserts the exact URL and verbatim body to guard against field drift.Testing
Release
Changeset included:
@gmc-cli/cli→ 1.0.16,@gmc-cli/api→ 0.9.21,@gmc-cli/auth→ 0.7.3 (all patch, per the post-1.0 patch-per-deliverable cadence).