> For the complete documentation index, see [llms.txt](https://docs.didomi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.didomi.io/consent-management-platform-cmp/frameworks-regulations/iab-tcf/view-vendors-and-associated-purposes.md).

# View vendors and associated purposes

**Option 1)** There's an easy way to see it directly in the vendors' view. For example, for Smart ad server, you need to click on the "view partners" link in your CMP, and then click on the vendor for which you wish to see the purposes.

**Option 2)** 

1. *A) Not IAB vendors* : Vendors and associated purposes can be called on */metadata/partners* (not the "vendors" but 'partners' section in the following documentation about metadata: <https://api.didomi.io/docs/#/partners-storages>.)\
   Please note that the endpoint partners is not listed in the above but it's the right one to call.&#x20;
2. B) *IAB Vendors* : the information is nested within the GVL ; <https://vendor-list.consensu.org/v3/vendor-list.json>


---

# 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.didomi.io/consent-management-platform-cmp/frameworks-regulations/iab-tcf/view-vendors-and-associated-purposes.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.