We’ve identified an inconsistency in our v2 product webhooks where date fields are deviating from our documented specifications. Currently, v2 product webhooks use YYYY-MM-DD HH:mm:ss format. To ensure consistency across our ecosystem, we are updating these to the RFC 3339 format (e.g., 2026-01-01T12:00:00Z).

On April 1st, 2026, this behavior will be updated. All date-related fields within v2 product webhooks will transition to the RFC 3339 standard with UTC timezones.

What does it mean for me?

If you consume v2 product webhooks, you must ensure your integration can handle RFC 3339 formatted strings. The following fields (and any other product-specific date fields) are included in this update:

• timestamp in the event meta object
• add_time
• update_time

We recommend updating your date parsing logic to be RFC 3339 compliant before the effective date to avoid any disruptions in data processing.

Additional resources:

• Guide for Webhooks v2

If you have any questions or comments, feel free to let us know in the Developer’s Community.