What changes without notice
- Adding a new endpoint, a new optional parameter, or a new field to a response body. Parse responses permissively — an unrecognised field is not an error and will not be announced.
- Widening what an existing parameter accepts, or adding a value to an OPEN vocabulary (source registries, form types, language codes). A closed enum gaining a value is announced. On the Events and Stories list and summary endpoints this includes serving a request as the canonical one it can only mean, reported in
applied_filters.normalized; such a rewrite is withdrawn only with the breaking-change notice period. - Correcting data. A score, a classification or a count that was wrong is fixed as soon as we know, and the changelog says so — waiting 30 days to stop serving a wrong number would be the opposite of a customer protection.
- Fixing a defect where the current behaviour is itself the hazard: a 200 hiding a wrong answer, a filter that silently does not apply, or a value we publish and then refuse.
Deprecated, retired, removed
Three different states. Only one of them stops working.
Older parameter names lists every older spelling, deprecated parameter, parameter that no longer applies and older
list key, with what to send instead.
How you are told
Response fields scheduled for removal
Still returned and still populated until the date below. Each is markeddeprecated in its
endpoint’s response schema.

