> For the complete documentation index, see [llms.txt](https://docs.goproxies.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.goproxies.com/proxies/self-service-dashboard/endpoint-generator.md).
# Endpoint Generator
Article describing how to access and use the endpoint generator
### Intro
This article will explain how to use the endpoint generator - a tool which you can find on our self-service dashboard.
### Walkthrough
1. Navigate to the Dashboard page and select “Endpoint Generator” on the top of the page.
2. In the selection fields below, select either HTTP or HTTPS as a protocol.
3. Select the subuser (also called the proxy user) from the drop-down,
4. Enter the subuser’s password (which would’ve been provided for you in a separate window when you first generated the subuser. If you’ve lost it, please navigate to the subusers page on the top right and reset your password there for that subuser, but please be sure to copy the password once it is shown in the new window again).
5. Select the country you’d like to target (optional)
6. Select the state from the state drop-down, which dynamically populates for the selected country. (optional)
7. Select the city from the city drop-down, which also dynamically populates for the selected state. (optional)
8. If you want to use session stickiness, check the “sticky” checkbox on the bottom right. (optional)
9. Under “number of endpoints”, select how many separate codes you’d like to generate. This is only relevant if you’ve checked “sticky”, as each line will have its own unique session ID needed for stickiness.
\
And you’re done! The code in the “Generated Endpoints” window will be auto generated based on the info you’ve entered earlier. Likewise, the “Integration Snippets” window gives you the code in various programming languages:
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.goproxies.com/proxies/self-service-dashboard/endpoint-generator.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
