Affects
Teams integrating with the Matcher API, especially clients that parse errors or retry requests with idempotency keys.
What changed
The documentation now correctly states that Matcher errors use an RFC 9457 problem envelope with
title, status, detail, and a stable code; field validation details use an errors array. It also documents the idempotency-key format (1–128 characters matching ^[A-Za-z0-9:_-]+$) and the retry behavior for MTCH-0015 and MTCH-0018.
This is a documentation correction; runtime behavior did not change.
Impact
Classification: Action required. Clients that parse the former
message or details fields, or generate idempotency keys without the documented constraints, must be aligned with the actual contract.
What you need to do
1
Update error handling to read
detail, status, and field-level errors where applicable.2
Validate generated idempotency keys against the documented length and character constraints.
3
Review retry handling for
MTCH-0015 and MTCH-0018 before the next integration release.