NFD API
  • NFDomains API
  • Quick Start
  • Reference
    • On-Chain Reference
      • On-Chain Diagram V3+
        • On-Chain Diagram V2+
        • V1 On-Chain Diagram
      • Registry Application IDs
      • Contract methods
      • Name & Address Lookup
        • V1 Resolution example (go)
          • Example PyTeal name/ID validity check
      • NFDs owned by Address
      • Reading of NFD metadata
      • Properties
      • Contract Changelog
    • NFDomains REST API Reference
    • Integrators Guide
      • Using an NFD for sending assets to Algorand accounts
      • Using an NFD to sending to non-Algorand chains.
      • Resolving an Algorand address to an NFD name / avatar
      • Interactive NFD lookup
      • Discord / Telegram bots
      • Linking an Application to an NFD
      • Using Vaults (2.x+)
      • Expirations / MBR liquidation
    • API Changelog
    • Status Page
  • Community
Powered by GitBook
On this page
  1. Reference

Integrators Guide

PreviousNFDomains REST API ReferenceNextUsing an NFD for sending assets to Algorand accounts

Last updated 10 months ago

Integrators, please take note of the guidance here as a consistent experience across the Algorand ecosystem is critical for users.

Make sure you're familiar with the 'views' of data as referenced at

Remember, NFDs are user-owned metadata on-chain, discoverable by name or Algorand address (including contract accounts !). Users and services (with users permission) can store whatever they want in their NFDs.

Services may use NFDs as user profiles if they wish. The user has already done the work. Just use that instead of creating your own profile system that is isolated to just your product.

Services may have preferences or other metadata that they want to share with other protocols they control, or even the broader ecosystem. They can provide transactions for the user to sign to update their NFD with that metadata and use that on-chain data easily via any Algorand node or smart-contract. Decentralized on-chain storage, owned by the user.

Refer to the subsequent sections for common access use-cases.

VIEWS in GET requests