Note: one of two different response schemas is returned based on whether the caller provides the user_data_type parameter. If included, a single UserDataAdd message is returned (or a not_found error). If omitted, a paginated list of UserDataAdd messages is returned instead.
API key to authorize requests
The FID that's being requested
The type of user data, either as a numerical value or type string. If this is omitted, all user data for the FID is returned Specifies which field of a user's profile is being updated.
USER_DATA_TYPE_PFP, USER_DATA_TYPE_DISPLAY, USER_DATA_TYPE_BIO, USER_DATA_TYPE_URL, USER_DATA_TYPE_USERNAME Maximum number of messages to return in a single response
Reverse the sort order, returning latest messages first
The page token returned by the previous query, to fetch the next page. If this parameter is empty, fetch the first page
The requested UserData.
"0xd2b1ddc6c88e865a33cb1a565e0058d757042974"
Type of hashing scheme used to produce a digest of MessageData. - HASH_SCHEME_BLAKE3: Default scheme for hashing MessageData
HASH_SCHEME_BLAKE3 Type of signature scheme used to sign the Message hash
SIGNATURE_SCHEME_ED25519, SIGNATURE_SCHEME_EIP712 Represents a message that updates a user's profile metadata. This can include changes to profile picture, display name, bio, URL, or preferred username. Each update modifies a single profile field.