curl --request GET \
--url https://api.fomoscan.sh/v2/user/wallet/{address} \
--header 'Authorization: Bearer <token>'const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
fetch('https://api.fomoscan.sh/v2/user/wallet/{address}', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://api.fomoscan.sh/v2/user/wallet/{address}"
headers = {"Authorization": "Bearer <token>"}
response = requests.get(url, headers=headers)
print(response.text){
"id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
"handle": "<string>",
"name": "<string>",
"bio": "<string>",
"banner": "<string>",
"profilePicture": "<string>",
"twitter": "https://x.com/tradername",
"solanaAddress": "<string>",
"evmAddress": "<string>",
"socials": [
{
"provider": "<string>",
"subject": "<string>",
"handle": "<string>"
}
]
}{
"error": {
"code": "BAD_REQUEST",
"message": "<string>",
"retryAfter": 123,
"addUrl": "<string>"
}
}Resolve a wallet address to the user(s) behind it
The same record as /v2/user/handle/{handle}.
- EVM addresses must be
0x-prefixed. The chain is inferred from the address. - 404 when we hold no user for the address.
- One record is returned even when the address is linked to more than one user. Repeat calls return the same one.
A response that carries a wallet counts as one of the plan’s monthly reveals.
Price: 30,000 CU on a hit, 200 CU on a 404.
curl --request GET \
--url https://api.fomoscan.sh/v2/user/wallet/{address} \
--header 'Authorization: Bearer <token>'const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
fetch('https://api.fomoscan.sh/v2/user/wallet/{address}', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://api.fomoscan.sh/v2/user/wallet/{address}"
headers = {"Authorization": "Bearer <token>"}
response = requests.get(url, headers=headers)
print(response.text){
"id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
"handle": "<string>",
"name": "<string>",
"bio": "<string>",
"banner": "<string>",
"profilePicture": "<string>",
"twitter": "https://x.com/tradername",
"solanaAddress": "<string>",
"evmAddress": "<string>",
"socials": [
{
"provider": "<string>",
"subject": "<string>",
"handle": "<string>"
}
]
}{
"error": {
"code": "BAD_REQUEST",
"message": "<string>",
"retryAfter": 123,
"addUrl": "<string>"
}
}Authorizations
B2B API key (fsk_live_… / fsk_test_…), issued by FomoScan. Also accepted via X-Api-Key.
Path Parameters
Solana address (base58) or EVM address (must include the 0x prefix).
1 - 128Response
Default Response
Stable FOMO user id. Unlike handle it never changes, so it is the key to store.
The canonical handle. Users rename — do not key on it.
Display name.
Profile blurb as written by the user, or null if they have none.
Cover photo URL on our image host, or null. The path is /a/<key>.webp. A new picture gets a new URL. A picture added in the last few minutes can show a neutral placeholder until it is ready.
Avatar URL on our image host, or null. The path is /a/<key>.webp. A new picture gets a new URL. A picture added in the last few minutes can show a neutral placeholder until it is ready.
Canonical X profile link, https://x.com/<handle>, or null. Normalised from whatever the user typed on FOMO; null when that could not be reduced to a plausible handle. Self-declared and NOT verified by us — a claim, not a proof.
"https://x.com/tradername"
Verified Solana address (base58), or null.
Verified EVM address, 0x-prefixed, or null.
Verified social account links. Present only when social account links are enabled on the API. Absent, not null, when they are not.
Show child attributes
Show child attributes