> For the complete documentation index, see [llms.txt](https://myty.gitbook.io/products/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://myty.gitbook.io/products/sdk/myty-sdk-interface/load-avatar.md).

# Load Avatar

## Background

To load avatar in MYTY Kit v1.2 or higher, we should provide two files. 1) shared metadata for collection, 2) the description and image trait file for each token ID. To get these information, you can refer to our Avatar Registry.

{% content-ref url="/pages/EpEePimGc8qiKo2IcipG" %}
[Avatar Registry(API)](/products/sdk/avatar-registry-api/overview.md)
{% endcontent-ref %}

## Input parameters

### AvatarCollectionId

ID of <mark style="color:purple;">`AvatarCollection`</mark> from Avatar Registry. When loading avatars with different token IDs, but with same <mark style="color:purple;">`AvatarCollectionId`</mark> , shared metadata will be used.

### MetadataAssetUri

This parameter refers to the URI for collection metadata. This is available in Avatar Registry.

### TokenId

TokenId is required to identify which NFT is mapped to MYTY Avatar. The pair of <mark style="color:purple;">`AvatarCollectionId`</mark> and <mark style="color:purple;">`TokenId`</mark>  allow users to specify MYTY Avatar.

### TokenAssetUri

This parameter refers to the URI for token description and image trait(zipped). This is available in Avatar Registry.

## Example Usage

```javascript
function loadAvatar(avatarCollectionId: number, metadataAssetUri: string, tokenId: string, tokenAssetUri: string)
{
  sendMessage("MessageHandler", "LoadAvatar", JSON.stringify({
    avatarCollectionId: avatarCollectionId,
    metadataAssetUri: metadataAssetUri,
    tokenId: tokenId,
    tokenAssetUri: tokenAssetUri
  }))
}
```