Our application is collecting data from the Markets API using GraphQL and API version 2027-04. The initial import is working as expecting when our application fetches the data it retrieves all market conditions. Unfortunately later on if the conditions are changed (condition added, removed or updated) no webhook is provided to notify of any change to the markets which means the data previously collected is out of sync.
Would it be possible to add webhooks for those events? There is already a markets/update topic which could be used for those events.
See below for a couple of sample scenarios;
- Region added/removed to regions condition
- Company location added/removed to company locations condition
Hey Mathieu,
Making changes to a market condition such as adding and removing regions or company locations will trigger the markets/update webhook. The payload currently does not include the specific changes so you will need to re-fetch the market conditions via the GraphQL API upon receiving the markets/update webhook in order to keep the data in sync.
Hope this helps!
@Aaron_Ebejer thank you for your reply. Our application already supports fetching the data from GraphQL when the webhook is received but I can guarantee that on our dev stores in the scenarios I provided no markets/update webhook is triggered.
As an additional note if a region is added or removed to the conditions a markets/update webhook is triggered.
As an additional note if a region is added or removed to the conditions a markets/update webhook is triggered.
So to confirm, it is working as expected for region conditions but not working for non-region conditions?
Can you check if your webhook api_version is set to version 2025-04 or greater? We have some filtering in place to prevent markets/update webhooks from being emitted for non-region markets on webhook subscriptions for older api_versions. I’m wondering if you are running into that filtering.
@Aaron_Ebejer yes this is correct it does not work for non-region conditions.
I have tested this with API version 2025-04 and 2025-07.
@Aaron_Ebejer following more testing I have worked out that the reason we are not seeing all webhook updates for market updates is due to debouncing. If I update market conditions for the same market within minutes only a single webhook is sent for the initial update. This is due to the minimal content of the market webhook which does not include the market conditions or an updated_at field. Can you please fix this asap? I can see 2 solutions;
- Disable debouncing for market updates
- Add field to market webhooks to prevent debouncing