X API
GET /1.1/users/search.json endpoint removal
Deprecated, no dateSubscribe to X APIShare
On September 28, 2023, X API deprecated GET /1.1/users/search.json without a shutdown date. Calls to this endpoint will fail. The change applies to all requests targeting the v1.1 user search functionality.
Calls it hits
GET /1.1/users/search.json
What to use instead of these calls
Look users up with the X API v2 (GET /2/users/by). Moving to this replacement takes more than changing an identifier, as X API v2 has no free-text user search in place of users/search and requires usernames to look users up.
X API v2 has no free-text user search in place of users/search; looking users up needs their usernames.
In X API's words
Today, we are deprecating the search/tweets, users/search, and geo/search endpoints in the X API v1.1.
Facts
- API
- X API
api.x.com - Kind
- Endpoint removal
- Announced
- September 28, 2023
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against X API's own pages
Questions
When does this change take effect?
X API deprecated GET /1.1/users/search.json without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: X API has not given a shutdown date yet.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from X API 3
-
No date
GET /1.1/geo/search.jsonEndpoint removal Deprecated, no date -
No date
GET /1.1/search/tweets.jsonEndpoint removal Deprecated, no date -
No date
POST /2/account_activity/replay/webhooks/{id}/subscriptions/allEndpoint removal Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.