In this guide, we’ll go over how to use our POST frame/action
API to handle frame interactions on your backend.
@neynar/react
SDK, see our Wownar React SDK examples.
POST frame/action
APIsigner_uuid
: the Neynar Signer UUID for the user who is taking the frame action, which would be retrieved through using Sign In with Neynar
cast_hash
: the hash of the cast from which the frame action is taking place
0xfe90f9de682273e05b201629ad2338bdcd89b6be
action
: the object of the frame being interacted with, including the interacted with button/action, which can normally be retrieved from the Neynar APIs
POST frame/action
API. Those actions are:
post
and redirect
: these actions should be handled on the client either as a window.replace
or as a link to a new tabmint
and tx
: the mint/transaction data itself should also be handled on the client, as the data from the frame object should have enough information to use in a package such as wagmi
or viem
. Here’s an example from our wownar-react-sdk repo.POST frame/action
API. Make sure to share what you built with us on Farcaster by tagging @neynar, and if you have any questions, reach out to us on Warpcast or Slack!