/v1/farcaster/* → version retirement
Neynar API
Stopped working
On March 31, 2025, Neynar API will shut down all API v1 endpoints. Requests targeting /v1/farcaster/* will fail after this date as the endpoints are fully turned off. Any integration still sending requests to these paths will no longer receive valid responses.
Calls it hits
/v1/farcaster/*
What to use instead of these calls
Switch to the v2 counterparts under /v2/farcaster/, such as GET /v2/farcaster/user/bulk/, GET /v2/farcaster/cast/, and GET /v2/farcaster/feed/. Developers using the Node.js SDK must update to Node.js SDK v2, which supports only API v2.
In Neynar API's words
All v1 APIs ( /v1/farcaster/* ) will be fully turned off on March 31, 2025.
Facts
- API
- Neynar API
api.neynar.com - Kind
- Version retirement
- Takes effect
- March 31, 2025
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Neynar API's own pages
Questions
When does this change take effect?
Calls to /v1/farcaster/* on Neynar API stopped working on March 31, 2025.
What happens to calls after March 31, 2025?
They have failed since March 31, 2025.
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 Neynar API 1
-
No date
GET /v2/farcaster/login/authorizeEndpoint removal Deprecated, no date
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.