Jump to content

Webhook payload.


Recommended Posts

I keep going back to the verbosity of the payload throwing everything and the kitchen sink to whom ever you send a web hook to to / Zappier < insert > third party. There is a lot of trust that must be had with these services as there is way too much PII info in the payload that is not necessary for 99% of the bits needed for taking action on. I've queried this before but have not got adequate answer as to when we can restrict what bits get issued in the payload. 

Link to comment
Share on other sites

18 minutes ago, Ocean West said:

I've queried this before but have not got adequate answer as to when we can restrict what bits get issued in the payload. 

As far as I remember we said that we won't change this in the 4.x lifetime.

By the way, not sure if you noticed this, but PII data are only included in the response when authorization happened with a generic API KEY.
If you use the REST API and GraphQL with oAuth authentication, all sensible data are stripped.

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...