> For the complete documentation index, see [llms.txt](https://integrations.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://integrations.impact.com/brand-api-reference/reference/tracking-value-requests.md). # Tracking Value Requests *Tracking value requests* are used by partners to request specific tracking values (Promo Codes, Unique URLs, and Phone Numbers) that they can use. You can use this endpoint to view your tracking value requests as well as approve or reject them. Attend to tracking value requests so you can ensure partners have everything they feel they need to successfully drive traffic. See the [Requests screen](https://app.impact.com/secure/advertiser/engage/ads/manage-all-ad-requests-flow.ihtml) to manage tracking value requests via the impact.com web app. Note that all ad and tracking value requests will appear here, but this endpoint will only let you manage requests for *tracking values*. --- # 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://integrations.impact.com/brand-api-reference/reference/tracking-value-requests.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.