Lightspark · Deprecation
Lightspark deprecation
Read from Lightspark's own page on 2026-11-09. 5 statements quoted word for word; anything the page does not say is shown as unstated, never guessed. APIs.io verifies none of it.
Minimum notice
period: at least three months
The migration window is normally at least three months; updates critical to security or compliance may require faster action.Read from Lightspark's own page on 2026-11-09
Support window
After the window, deprecated versions are no longer supported.Read from Lightspark's own page on 2026-11-09
Announcement channels
channel: email
When we deprecate a version, we notify your account contact email with the migration steps and a deadline.Read from Lightspark's own page on 2026-11-09
Deprecation / Sunset headers
Versioning scheme
value: date-based major version in base URL
The date in the base URL is the API’s major version.Read from Lightspark's own page on 2026-11-09
Breaking change definition
Breaking changes — removing or renaming fields or endpoints, changing types, or making optional parameters required — ship only in a new dated version.Read from Lightspark's own page on 2026-11-09
Document
Download YAML · schema: API Commons Deprecation 0.1.0 · transcribed by claude-haiku-5-5, checked verbatim against the fetched page