Resolved on July 13, 2026.
SEEK recently updated the way webhook events are delivered, including a change to the casing of HTTP headers on those requests. This may have impacted integrations that incorrectly treat HTTP header names as case-sensitive, even though HTTP header field names are case-insensitive under RFC 9110. For reference: RFC 9110, section 5.1 https://www.rfc-editor.org/rfc/rfc9110.html#section-5.1 This affected all webhook events sent between 2026-07-14 16:00:00 and 2026-07-15 14:30:00 AEST. To mitigate the affect of this issue SEEK are replaying all webhook events that were sent during the incident window.
Update timeline
- resolved Jul 16, 2026, 05:03 AM UTC
SEEK recently updated the way webhook events are delivered, including a change to the casing of HTTP headers on those requests. This may have impacted integrations that incorrectly treat HTTP header names as case-sensitive, even though HTTP header field names are case-insensitive under RFC 9110. For reference: RFC 9110, section 5.1 https://www.rfc-editor.org/rfc/rfc9110.html#section-5.1 This affected all webhook events sent between 2026-07-14 16:00:00 and 2026-07-15 14:30:00 AEST. To mitigate the affect of this issue SEEK are replaying all webhook events that were sent during the incident window.
Your product runs on more than SEEK
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services