> For the complete documentation index, see [llms.txt](https://docs.dokidoki.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dokidoki.com/resources/for-developers/supported-metadata-structures.md).

# Supported metadata structures

## OpenSea metadata standards

If your NFTs use the [OpenSea metadata standards](https://docs.opensea.io/docs/metadata-standards#metadata-structure), you are already good to go.

## Other structures

If you don't follow the above standards, worry not, you might still be using the following structures:

| Type of data                     | Key in your metadata               |                                                                                                                                                                                                                                                                                                                         |
| -------------------------------- | ---------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Image (PNG, JPEG, JPG, GIF only) | <p>image</p><p>image\_url</p>      | The image that represents your NFT, we will use that key to generate the preview of your NFT. Any other file format than an image will be rejected.                                                                                                                                                                     |
| Video (MP4 Only)                 | animation\_url                     | Video of your NFT, usually the full resolution display of it. **If your structure contains this key, it MUST also contains the preview in the "image" category.**                                                                                                                                                       |
| name                             | name                               | The name of your NFT that will be displayed on our site.                                                                                                                                                                                                                                                                |
| description                      | description                        | The description of your NFT                                                                                                                                                                                                                                                                                             |
| Attributes                       | <p>attributes</p><p>properties</p> | <p>An array of properties with the following format:</p><p><code>\[</code></p><p>  <code>{</code></p><p>     <code>"trait\_type": "name of property",</code></p><p>     <code>"value": "value of property"</code></p><p>  <code>},</code></p><p>  <code>{...},</code></p><p>  <code>...</code></p><p><code>]</code></p> |

Any other data will not be taken into account.

## My NFTs don't follow any of those structures :(

Worry not! You can still use our gachapons, but the NFTs might not be displayed properly (No preview, no name...).

If you want them to be supported, you can just contact us beforehand on Discord or Telegram. We will do our best so they can be integrated ASAP.


---

# 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://docs.dokidoki.com/resources/for-developers/supported-metadata-structures.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.