HTTP Accept headers for webhooks now specify JSON during Issuing authorizationsBreaking changes
What’s new
Webhooks emitted for Issuing real-time authorizations now specify application/json in the request Accept header. This change improves the clarity of content negotiation, because real-time authorization webhooks require a JSON response from your integration.
Why is this a breaking change?
Your webhook handler might return an HTTP response code 406 if it doesn’t support JSON as a response format. These errors are visible in Workbench. If you use Issuing real-time authorizations, a response code other than 200 might cause your authorizations to decline.
Impact
Issuing real-time authorizations require JSON responses to issuing_ webhooks. Those webhooks’ Accept headers now specify application/json in order to align with that requirement.