> For the complete documentation index, see [llms.txt](https://jollyproxy.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://jollyproxy.gitbook.io/docs/feature-configuration/whitelist.md).
# Whitelist
{% hint style="danger" icon="exclamation" %}
**Usage Notice**: All JollyProxy proxy products must be used in an overseas network environment. Please ensure that you have configured the corresponding overseas network environment yourself.
{% endhint %}
This article will explain how to configure a **Whitelist** on the **JollyProxy** platform so that you can securely obtain proxy information through the API interface.
### **I. Log In to the Proxy Platform**
Open your browser and visit the [JollyProxy official website](https://www.jollyproxy.com/zh-cn/login). Enter your account and password to log in to the system.
### **II. Manage the Whitelist**
**1. Go to the management page**
After logging in successfully, click **Sub-Accounts** in the left sidebar.
**2. Delete a whitelisted IP**
In the whitelist, find the IP address you want to delete and click the **Delete** button on the right to remove it.
**3. Add whitelist entries in bulk**
If you need to manually add multiple IP addresses:
* Enter the IP addresses in the input box (one per line)
* Optionally fill in remarks for easy identification and management
* Click the **Add** button to complete the addition
---
# 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://jollyproxy.gitbook.io/docs/feature-configuration/whitelist.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.
