Repository navigation
[D2] Document the ecommerce product events endpoint (Preview) - #719
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
rkaahean
marked this pull request as ready for review
October 14, 2026 08:12
harish-intercom
approved these changes
Oct 14, 2026
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.
Why?
Ecommerce connectors can now send single product changes (created, updated, deleted) instead of re-uploading the whole catalog, so product answers stay current between full uploads. The endpoint is available in Preview but isn't in the spec, so developers can't find it or see how to call it.
How?
Adds the events operation to the Preview spec next to the catalog upload, with request examples for each event type, the error responses, and the rules for events that arrive out of order.
Notes for reviewers
The request schema keeps
data.productanddata.product_idas optional properties of one object instead of aoneOfper event type. Which field each type needs is stated in the field and operation descriptions, and the API rejects a mismatched event with400 invalid_event. A one-schema-per-type split would turn the request into a union in generated SDKs for a rule the server already enforces.Generated with Claude Code