409 Conflict is now listed in the Error Handling guide
The status-code table in Error Handling listed
400 401 402 403 404 405 429 502 503 and omitted 409, which
GET /v1/markets/{market_id} and GET /v1/events/{event_id} have returned
since ambiguous bare identifiers stopped resolving to the wrong provider's
market on 2026-08-25.
Nothing about the API changed. 409 was declared on both operations in the
OpenAPI spec from the day it shipped and generates as a typed error in all three
SDKs — but a caller who built their error handling from that page had no 409
branch, and the page is the one place that says which statuses to retry. It now
carries a row and an entry under Retry guidance: 409 is a do-not-retry-unchanged
case, because the identifier is genuinely ambiguous and the same request
conflicts again. Re-send with ?platform= naming one of the candidates in the
response body, or with the composite {platform}:{id} form.
Both of that page's hand-maintained lists — the status-code table and the retry
bullets — are now checked against the spec on every CI run, in both directions.
A status code declared on an operation and missing from either list fails the
build, and so does a code listed on the page that no operation declares. The two
router-level statuses documented at the API level rather than per operation
(404 for an unrouted path, 405 for a rejected method) are exempt from
needing an operation response, and the check requires them to still be
documented at the API level rather than taking that on trust.