> 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
  }))
}
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://myty.gitbook.io/products/sdk/myty-sdk-interface/load-avatar.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.