The deprecated flat routes now retire on 9 December
The retirement date of the deprecated flat routes moves from 10 September to 2026-12-09. Nothing stopped answering, and you have the whole window again.
The flat routes deprecated when resources moved under the NIF carried a Sunset of 10 September 2026. That day came, the routes kept answering, and the date is now where it should have been: 2026-12-09.
It moved in every place at once — the Sunset header on the responses, the deprecated notices in the reference, and the migration guide — so there is one date to track, not two.
What else changed
- Nothing broke and nothing was removed. Every deprecated route answered on 10 September and answers today.
- A published date moves later, never sooner. That is the commitment in the deprecation policy: if we get a retirement date wrong, it is pushed out, never brought forward.
- The 91 deprecated operations carry the new date in their
Sunsetheader, each with its successor route where it has one. The fastest audit is still your own logs: grep a day of responses forDeprecation: true. - The migration itself has not changed — the route table in Resources under the NIF is the same. Only the deadline moved.
Where to go next
Recurring writes reject what they used to swallow
Payment detail without a method, an inactive series, a window with no occurrence and a blank name are now rejected instead of silently discarded.
next_generation is null when there is no next invoice
`next_generation` now carries only the date the system will honour, and `null` otherwise: a completed template, or a paused one whose date has passed.