/opensea/accounts

POST /api/opensea/accounts

Price: 1 credit

Get an OpenSea account profile by wallet address, username or ENS name

How to use it

Get an OpenSea account profile by a wallet address, OpenSea username or ENS name. Returns the wallet address, display name, username, ENS name, account kind, avatar and banner images, bio, external url, linked twitter and instagram, verification status, join date, and follower and following counts.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• identifier string required — Account identifier: a wallet address, OpenSea username or ENS name (examples: "pranksy", "vitalik.eth", "0xd387a6e4e84a6c86bd90c158c6028a58cc8ac459"; minLength: 1)

Response

• @type string (default: "OpenseaAccount")
• address string required
• display_name string nullable
• alias string nullable
• ens_name string nullable
• account_id string nullable
• kind string nullable
• image string nullable
• banner string nullable
• bio string nullable
• external_url string nullable
• twitter string nullable
• instagram string nullable
• is_verified boolean (default: false)
• is_compromised boolean (default: false)
• joined_at string nullable
• follower_count integer nullable
• following_count integer nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — Account not found Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.