Deprecations

One Vastu rules snapshot is deprecated, with a sunset date and a replacement. Here is the policy for deprecations.

#Currently deprecated

Important

One item is deprecated: the Vastu rules snapshot vastu-rules-2026-09-23. It is still accepted until its sunset date.

Item	Deprecated from	Deprecation header	Sunset	Replacement	Status
Vastu rules snapshot `vastu-rules-2026-09-23` (`rulesVersion` pin)	2026-10-18	`Deprecation: @1792281600`	Sun, 31 Jan 2027 00:00:00 GMT	`vastu-rules-2026-10-20`	Still accepted until the sunset date

A response that applied vastu-rules-2026-09-23 carries Deprecation, Sunset and Link headers; a batch carries them when at least one item was evaluated under it. Other versions carry none. Async job results carry no HTTP headers; read rulesVersion in each item result. See the changelog.

#Deprecation policy

Breaking changes ship behind the version parameter (for example "2" vs "2.5" on the standard path), so an existing integration keeps its current behaviour until it opts in.
Deprecations get advance notice through the changelog and by email to registered account contacts — not a silent removal.
A pinned version stays available for the duration of its stated support window, not just until the next release.

#Pin your version

If a build is going to run unattended for a while, pin version explicitly instead of relying on the default, and keep an eye on the changelog for when a newer version is worth adopting.

{
  "question": "...",
  "birthDetails": { "...": "..." },
  "speed": "standard",
  "version": "2"
}