Content
@
https://opensea.io/collection/neynar-1
0 reply
0 recast
0 reaction
greg
@gregfromstl
@rish is it possible to use the client ID with the neynar API rather than the API key if I’m making the request from an authorized origin?
1 reply
0 recast
3 reactions
rish
@rish
What’s the use case? @manan @shreyas-chorge
1 reply
0 recast
0 reaction
greg
@gregfromstl
I want to be able to call the API from the frontend so I can statically generate the full site
1 reply
0 recast
0 reaction
Manan
@manan
we've allowlisted a specific set of APIs that are used in @neynar/react to work with a client id + frontend origin. we can add more to the list if it helps
1 reply
0 recast
1 reaction
greg
@gregfromstl
Post cast endpoint?
1 reply
0 recast
0 reaction
Manan
@manan
unfortunately not since it would reduce the security guarantees of neynar managed signers. Authorized origin can be spoofed and client id + signer uuid can be inspected on network traffic. We have allowlisted POST /v1/submitMessage which submits directly to the snapchain but then you have to take on the responsibility of managing the signer locally on the client.
0 reply
0 recast
1 reaction
