GET /v2/farcaster/login/authorize → endpoint removal
Neynar API
Deprecated, no date
Neynar deprecated the GET /v2/farcaster/login/authorize endpoint without a shutdown date. The provider noted that Sign In With Neynar is being retired. Calls to this endpoint will eventually fail.
Calls it hits
GET /v2/farcaster/login/authorize
What to use instead of these calls
Use Neynar-managed signers by calling POST /v2/farcaster/signer/ followed by POST /v2/farcaster/signer/signed_key/ as described in Neynar's managed signers guide. Moving to managed signers requires more than changing an identifier, as it alters the login and signer flow.
Sign In With Neynar has no drop-in endpoint: moving to managed signers changes the login and signer flow.
In Neynar API's words
DEPRECATED: Sign In With Neynar is being retired. Use Neynar-managed signers instead
Facts
- API
- Neynar API
api.neynar.com - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Neynar API's own pages
Questions
When does this change take effect?
Neynar API deprecated GET /v2/farcaster/login/authorize without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Neynar 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 Neynar API 1
-
/v1/farcaster/*Version retirement Stopped working
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.