We’ve identified an issue where the v2 user webhooks are deviating from the documented specification. According to our Webhooks v2 documentation, the timestamp field in the event meta object should be an RFC 3339 formatted timestamp (e.g., "2025-01-01T00:00:00.000Z"). However, the current implementation returns timestamps as UNIX timestamps (seconds since 1970) instead.

On June 30th this behaviour will be rectified to reflect our documentation and user webhooks meta timestamp will be switched to RFC 3339 format.

What does it mean for me?

		<p>If you are consuming v2 user webhooks and rely on the <code>timestamp</code> field in the event meta object, make sure your application can process the updated RFC 3339 format. This change only affects v2 <b>user</b> webhooks — all other v2 webhooks (including activity, deal, lead, note, organization, person, pipeline, product, and stage) are already using the correct timestamp format and are not impacted by this fix.</p>

  <h2>Additional resources:</h2>
  <ul>
    <li><a href="https://pipedrive.readme.io/docs/guide-for-webhooks-v2">Guide for Webhooks v2</a></li>
  </ul>      
  
  <p>If you have any questions or comments, feel free to let us know in <a href="https://devcommunity.pipedrive.com/">the Developer’s Community</a>.</p>