---
title: "Resolve an account identifier"
method: GET
path: "/api/v2/accounts/resolve/{identifier}"
tags: ["Account Endpoints"]
---

# Resolve an account identifier

`GET /api/v2/accounts/resolve/{identifier}`

Resolve an ENS name (e.g. vitalik.eth), OpenSea username, or wallet address to canonical account info including address, username, and ENS name. The ENS path performs both forward resolution (name → address) and reverse lookup (address → canonical primary name). The address and ENS paths perform enrichment calls (username + ENS reverse lookup) in parallel. The username path only needs an ENS reverse lookup after the initial resolution and runs it sequentially. The ENS and username paths require an extra initial call and may be slower than the address path on cache misses.

## Path parameters

- `identifier` string, required

## Response `200`

Resolved account info

## Other responses

- `400` — For error reasons, review the response data.
- `401` — Unauthorized
- `403` — Forbidden
- `404` — Resource not found
- `409` — Conflict
- `500` — Internal server error. Please open a support ticket so OpenSea can investigate.

---

[API](https://skmtc.net/opensea/apis/opensea-api.md) · [All operations](https://skmtc.net/opensea/apis/opensea-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/opensea/opensea-api/versions/acee8835f2ae/schema)