Remove dheCipherSuite field and 409/500 response codes from API spec
BreakingBreaking change
This is a breaking change — integrations that rely on the affected behaviour will need updates before the change rolls out.
What changed
Two distinct breaking changes are present: 1) The dheCipherSuite response field (type string) has been removed from multiple log/event response schemas — it also appears in required arrays, meaning clients that rely on its presence will break. 2) The 409 and 500 response status codes have been removed from one endpoint's documented responses, which may affect error-handling logic in clients that branch on those codes.