New fields added in GET /v3/user/webhooks/event/settings/{id} (EventWebhookNoDatesResponse): [enabled, oauth_client_id, bounce, url, group_resubscribe, open, pu…
New fields added in GET /v3/user/webhooks/event/settings/{id} (EventWebhookNoDatesResponse): [enabled, oauth_client_id, bounce, url, group_resubscribe, open, public_key, delivered, dropped, account_status_change, friendly_name, spam_report, unsubscribe, group_unsubscribe, processed, id, click, deferred, oauth_token_url]
- Affected surface
- GET /v3/user/webhooks/event/settings/{id}
- Affected field
- EventWebhookNoDatesResponse
What changed
New fields added in GET /v3/user/webhooks/event/settings/{id} (EventWebhookNoDatesResponse): [enabled, oauth_client_id, bounce, url, group_resubscribe, open, public_key, delivered, dropped, account_status_change, friendly_name, spam_report, unsubscribe, group_unsubscribe, processed, id, click, deferred, oauth_token_url] Affected surface: GET /v3/user/webhooks/event/settings/{id}. Root cause: schema `EventWebhookNoDatesResponse`. Detected at Thu, 20 Jun 2024 14:42:14 UTC UTC.
Diff
{
"added_fields": [
"enabled",
"oauth_client_id",
"bounce",
"url",
"group_resubscribe",
"open",
"public_key",
"delivered",
"dropped",
"account_status_change",
"friendly_name",
"spam_report",
"unsubscribe",
"group_unsubscribe",
"processed",
"id",
"click",
"deferred",
"oauth_token_url"
],
"path": "GET /v3/user/webhooks/event/settings/{id}",
"schema_path": "schema EventWebhookNoDatesResponse"
}Likely impact
This is an additive change. Existing integrations are unaffected; this is mostly useful if you want to take advantage of the new surface.
Recommended action
Diff your serializers against the new schema. The diff above shows what moved.
Related changes
Other endpoints affected by the same root cause.
Catch changes like this on every API you depend on.
Intello monitors 100+ APIs and tells you the moment something changes — before it breaks production.