Skip to main content
The Xquik REST API is v1, and v1 stays compatible. We add fields, parameters & endpoints without notice. Your client should ignore fields it doesn’t know. This policy has applied since 2026-08-26.

​
Notice for breaking removals

  • We announce a breaking removal at least 90 days before it happens.
  • A deprecated part keeps working until its removal date.
  • The changelog announces each new deprecation & removal. The tables below list today’s with their dates.
  • OpenAPI marks each deprecated operation, parameter & field deprecated: true.

​
Exceptions

  • If X stops running a feature, no request can return its data. Xquik then answers 424 right away & charges nothing.
  • A security or legal emergency may shorten the notice.
  • The changelog explains each exception.

​
Headers on deprecated requests

A request with a deprecated query parameter or search filter gets these headers. GET /api/v1/account sends them too, because its answer still has monitorsAllowed. OpenAPI declares them on each success answer that sends them.Log these headers in your client. A Deprecation header means a change is due. A Sunset header gives the date.

​
Scheduled removals

From 2027-01-15 such an extraction answers 424 search_unavailable & charges nothing.

​
Deprecated with no removal date

OpenAPI is the full list. It marks a few more fields deprecated that send no header. POST /api/v1/compose ignores hasLink. It returns radarRecommendations & examplePatterns empty. Monitor events keep userName & rawVerified. Read username & verified instead.

​
Check your integration

  1. Search your code for the items in the tables above.
  2. Watch for Deprecation & Sunset headers in responses.
  3. Read the changelog before each upgrade.
The same policy is published as Markdown at xquik.com/deprecation-policy.md.