How do reconciliation job for returns?

Webhook documentations says

Note:

Although it is not often, it is possible for a webhook not to fire, and that is why your app should not rely just on receiving data from our webhooks.
The webhook delivery is not always guaranteed, so we strongly suggest implementing reconciliation jobs to periodically fetch data from ShipHero.
Our most important Queries have both thecreated_at_min and updated_at_minfilter parameters., which will allow you to build a job that fetches all resources that have been created or updated since the last time the job ran.

I am listening to Return Update webhooks currently.

But how would I do a reconciliation job that would ensure consistency? I do not see any “update at” field.

1 Like

Also curious if there’s a solution for this. The returns API endpoint doesn’t offer much if anything regarding historical data/actions/updates made to returns.

Hello,

Thanks for reaching out. We don’t currently support any updated_at filter fields for returns in the API only the date created via date_from and date_to. I can submit a request for this addition for review by our product team.

In the return query there is an array of return_history that records dates of the log entry creation. This can be used in the meantime to filter new updates with an external algorithm.

I will follow up here if we receive updates on adding the filter field to the query.

1 Like