> For the complete documentation index, see [llms.txt](https://docs.sprinthub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinthub.com/en/topics/api/api-getting-and-modifying-lead-tags.md). # API - Getting and modifying Lead tags How to view, remove, and add tags from a Lead. ### General Query Params

Key	Description
i	Your instance identifier, subdomain
apitoken	API Token

## Getting instance tags The request was sent using the software *Postman*. The expected response is a list of objects with the IDs and names of the tags in the instance. `GET` `/tags?apitoken=seu-token&i=sua-instancia` Full endpoint:

## Getting the Lead's current tags The expected response is a list with the tags linked to the Lead and their respective colors. `GET` `/leads/id-do-lead?query={tags{id,tag,color}}&apitoken=seu-token&i=sua-instancia` Full endpoint:

## Modifying the Lead's tags To modify the tags, an overwrite method is used. The tag IDs passed in the request body will replace the lead's current tags. You must pass an object with the key `tags` which has an array of IDs as its value. `PUT` `/leads/id-do-lead&apitoken=seu-token&i=sua-instancia` Full endpoint:

--- # 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.sprinthub.com/en/topics/api/api-getting-and-modifying-lead-tags.md?ask=&goal= ``` `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.