mobilevalidate-com · Deprecation
mobilevalidate-com deprecation
Read from mobilevalidate-com's own page on 2026-11-10. 7 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: 12 months
v1 keeps working unchanged for **at least 12 months** after the new version and the v1 retirement date are announcedRead from mobilevalidate-com's own page on 2026-11-10
Support window
period: 12 months
The sunset date is at least 12 months after the announcement.Read from mobilevalidate-com's own page on 2026-11-10
Announcement channels
channel: changelog
We publish a changelog entry with the tag "API" (also in the [RSS feed](/changelog/rss.xml))Read from mobilevalidate-com's own page on 2026-11-10
channel: email
We e-mail the contacts of the accounts that use it.Read from mobilevalidate-com's own page on 2026-11-10
channel: other
The documentation marks it as deprecated.Read from mobilevalidate-com's own page on 2026-11-10
Deprecation / Sunset headers
Versioning scheme
value: URL path major version (v1, v2)
The MobileValidate API is versioned in the URL path.Read from mobilevalidate-com's own page on 2026-11-10
Breaking change definition
Removing or renaming an endpoint, field, parameter or enum value; changing a field's type or meaning; making an optional request field required; changing authentication; changing an HTTP status for an existing situation; or lowering a documented limit.Read from mobilevalidate-com's own page on 2026-11-10
Document
Download YAML · schema: API Commons Deprecation 0.1.0 · transcribed by claude-haiku-5-5, checked verbatim against the fetched page