🥷
Namespace
  • [ Introduction ]
    • ENS
    • Namespace
      • Products and Services
      • Use Cases
  • [ Namespace Platform ]
    • Overview
    • Search & Registration
    • Manager
      • Listing an ENS Name
      • Features List
    • ENS Widget
    • Farcaster Frames
      • Default Frame
      • Custom Frame
    • Tutorials and Demos
  • [ Dev Docs ]
    • Overview
    • How-To Guides
      • Mint L1 or L2 subnames using SDK
    • Smart contracts
      • Namespace Minter
    • Backend API
      • POST /api/v1/mint
      • POST /api/v1/mint/verified
      • GET /api/v1/listings/availabe
    • Offchain Subnames API
      • Setting Up Offchain Resolver
      • Minting
        • Create a new ENS subname
      • Subnames
        • Resolve subname address
        • Check subname availability
        • Retrieve Complete Subname Dataset
        • Subname Search
        • Delete Subname
      • Text Records
        • Create or update subname text record
        • Delete a subname text record
        • Retrieve single subname text record
        • Retrieve all of subname's text records
      • Custom Data
        • Create or update custom subname data
        • Delete custom subname data
        • Retrieve single custom data object
        • Retrieve all of subname's custom data
    • Namespace SDK
      • Offchain Manager
        • Installation
        • Methods
        • Generate API key
        • CreateSubname
        • DeleteSubname
        • IsSubnameAvailable
        • GetFilteredSubnames
        • TextRecords
        • DataRecords
      • Indexer Manager
        • Installation
        • Methods
        • GetL2Subname
        • GetL2Subnames
        • GetL1Subnames
        • GetL1Subnames
        • GetL1Subname
      • Mint Manager (soon)
      • Namespace Client (deprecated)
        • Installation
        • GetListedName
        • GetMintDetails
        • GetMintTransactionParameters
        • IsSubnameAvailable
        • GenerateAuthToken
    • Namespace L2 Subnames
  • [ ecosystem ]
    • Partnerships
    • Integrations
    • Links
    • ENS ideas and projects
  • [ Legal ]
    • Disclamer
    • Terms of Service
    • Privacy Policy
Powered by GitBook
On this page
  1. [ Dev Docs ]
  2. Offchain Subnames API
  3. Subnames

Resolve subname address

GET /v1/subname/resolution

PreviousSubnamesNextCheck subname availability

Last updated 10 months ago

In order to resolve the subname address and get the subname details, make a request to /subname/resolution/{address}/{coinType}:

  • address wallet address of the subname

  • coinType coin type as specified in

Refer to the Response Body section below for response details.

https://docs.ens.domains/ens-improvement-proposals/ensip-9-multichain-address-resolution
get
Path parameters
addressstringRequired

Expected address of the subname

coinTypenumberRequired

Expected coin type of the subname

Responses
200
Subnames matching the wallet and coin type search. Refer to SubnameResolutionResponse
500
Error with the message identifying which parameters caused the bad request.
application/json
default
application/json
get
GET /v1/subname/resolution/{address}/{coinType} HTTP/1.1
Host: 
Accept: */*

No content