POST
/
farcaster
/
user
/
verification
curl --request POST \
  --url https://api.neynar.com/v2/farcaster/user/verification \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: <api-key>' \
  --data '{
  "signer_uuid": "19d0c5fd-9b33-4a48-a0e2-bc7b0555baec",
  "address": "0x1ea99cbed57e4020314ba3fadd7c692d2de34d5f",
  "block_hash": "0x191905a9201170abb55f4c90a4cc968b44c1b71cdf3db2764b775c93e7e22b29",
  "eth_signature": "0x2fc09da1f4dcb723fefb91f77932c249c418c0af00c66ed92ee1f35002c80d6a1145280c9f361d207d28447f8f7463366840d3a9309036cf6954afd1fd331beb1b"
}'
{
  "success": true,
  "message": "<string>"
}

Authorizations

​
x-api-key
string
header
default:NEYNAR_API_DOCS
required

API key to authorize requests

Body

application/json
​
signer_uuid
string
required

UUID of the signer. signer_uuid is paired with API key, can't use a uuid made with a different API key.

Example:

"19d0c5fd-9b33-4a48-a0e2-bc7b0555baec"

​
address
string
required

Ethereum address

Example:

"0x5a927ac639636e534b678e81768ca19e2c6280b7"

​
block_hash
string
required
​
eth_signature
string
required
​
verification_type
enum<integer>
default:0

Type of verification. 0 = EOA, 1 = contract

Available options:
0,
1
​
chain_id
enum<integer>
default:0

Chain ID for farcaster verifications. 0 for EOA verifications, 1 or 10 for contract verifications

Available options:
0,
1,
10

Response

200 - application/json
Successful operation.
​
success
boolean
​
message
string

Was this page helpful?