Documentation changes for September 22, 2026
As part of an ongoing effort to better align the documentation with the API, we’ve corrected the notification log response schemas. These changes affect the documentation only; the API was already returning this data.
Documented additional fields on notification log responses
The notification log responses now document fields the API already returns. The search response documents requestId, notificationType, organizationName, organizationLogo, organizationFavIcon, paypointName, and paypointLogo. On the detail response, webHeaders, responseHeaders, and responseContent are now documented as always present. webHeaders and responseHeaders can return null — responseHeaders is null when the target sent no response. This affects:
Corrected the response status fields on notification log responses
The documentation described a single responseStatus string holding the HTTP status code. The API actually returns the HTTP status code in responseStatusCode (an integer, 0 when the target sent no response) and a status message such as OK, Dropped, or No response received from server. in responseStatus. Both fields are now documented on the endpoints above.
Corrected the retry response bodies
The single-retry endpoint was documented as returning the full notification log entry, but it returns a short confirmation message such as {"message": "Notification retry succeeded."}. The bulk-retry endpoint returns a plain-text confirmation. This affects: