Webhook null vs "null" change?

We noticed today, that since yesterday it seems the webhook json data is treating null differently.  ei:
"freshdesk_webhook": {
  "ticket_id" : 19,
  "ticket_cf_customfield" : "null"
}

Up till yeterday webhooks were sending out:

"freshdesk_webhook": {
  "ticket_id" : 19,
  "ticket_cf_customfield" : null
}

Was this an intentional change?  How are we to distinguish from the value null and a string null?  This is causing issues with our custom api integration.

This only seems to be affecting webhooks, not API responses.

 

1 Comment

From our contact at Freshdesk Support this issue appears to have been acknowledged as a bug:

 

We had this checked with our developers and this has been acknowledged as a bug by our developers. We would keep you posted with updates once this is fixed. 

 

 
The bug appears to have been resolved this weekend so thank you to whomever was involved.

Login or Signup to post a comment