> For the complete documentation index, see [llms.txt](https://guide.bocto.octopeeps.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.bocto.octopeeps.com/appendix/getting-collection-slug-symbol.md).

# Getting Collection Slug/Symbol

Before you proceed with adding a collection to the <mark style="color:blue;">**NFT Stats**</mark> or tracking its listings and sales with the <mark style="color:blue;">**NFT Tracker**</mark> or setting up a <mark style="color:$primary;">Specific Traits-Based Roles</mark> rule with the <mark style="color:blue;">**Verify Roles**</mark> plugin, you first need to prepare the <mark style="color:$success;">Collection Slug</mark> (for the collections listed on <mark style="color:$warning;">**OpenSea**</mark>) or the <mark style="color:$success;">Collection Symbol</mark> (for the collections listed on <mark style="color:$warning;">**Magic Eden**</mark>). Technically, this is absolutely the same thing, just named differently on these two marketplaces. So let's call it <mark style="color:$success;">Collection Slug</mark> for shot.&#x20;

Well, the <mark style="color:$success;">Collection Slug</mark> is a part of the marketplace collection URL in the browser address bar, normally located after the last slash, but not always.

## <mark style="color:$primary;">Collection Slug on OpenSea.</mark>

<figure><img src="/files/BU4PmHcFmrOMWXm0pguq" alt=""><figcaption></figcaption></figure>

## <mark style="color:$primary;">Collection Symbol on Magic Eden.</mark>

<figure><img src="/files/zuxWXDQV510u0kVrdJ29" alt=""><figcaption></figcaption></figure>

## <mark style="color:$primary;">Contract Address on LooksRare.</mark>

The collections listed on <mark style="color:$warning;">**LooksRare**</mark> do not have a <mark style="color:$success;">Collection Slug</mark>, and you don't need it. However, you will need the collection <mark style="color:$success;">Contract Address</mark>, which can be found in the same way, at the end of the collection URL.

<figure><img src="/files/CEkxBfI9pPbnf8SjfQqy" alt=""><figcaption></figcaption></figure>

## <mark style="color:$primary;">What's next?</mark>

Now, when you have your <mark style="color:$success;">Collection Slug</mark>, you can proceed with [adding a collection](/plugins/nft-stats/adding-new-collection-with-rarible.md) to the <mark style="color:blue;">**NFT Stats**</mark> or tracking a collection's listings and sales with the <mark style="color:blue;">**NFT Tracker**</mark> or setting up a [Specific Traits-Based Roles](/plugins/verify-roles/introduction.md#specific-traits-based-roles) rule with the <mark style="color:blue;">**Verify Roles**</mark> plugin.


---

# 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://guide.bocto.octopeeps.com/appendix/getting-collection-slug-symbol.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.