> For the complete documentation index, see [llms.txt](https://docs.tpi.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tpi.dev/most-common-use-cases/api-ip-diversion.md).
# API IP Diversion
APIs registered in the system can be configured to allocate IP traffic and restrict access.
This application is similar to the concept of double centers. Using the concept of branch company for explanation, Taipei IPs need to use Taipei APIs, and Kaohsiung IPs need to use Kaohsiung APIs; setting it properly will make them easier to manage and prevent errors from being accidentally triggered.
### Registering APIs
1. Go to **API Management** > **API Registry**, and click **CUSTOMIZE** to enter the registration page.
2. Fill in the required fields: **API Name, digiRunner Proxy Path** and **Http Methods**.
3. Since authentication is not required for now, select **No Auth**.
4. After selecting **Source IP diversion** for the **Target URL** field, click on the **+** icon to get two Source IP input boxes.
* Fill in the local IP for the first Source IP, and fill in the API address to call for the target URL.
* Fill in the Custom IP for the first Source IP, and fill in the API address to call for the target URL.
5. Click **Register** to complete the API registration.
### Calling API Verification Dispatch Function
1. Go to **API Management** > **API List**, and select the API, the status light is red  by default; click **Enable**.
2. A confirmation window will pop up, click **Confirm** to finish enabling the API, and the status light will turn green .
3. Click on the **Test** icon  to open the testing area.
4. Select **No Auth** for **Authorization**.
5. Click **Test** to view the response. Since the local IP is defined in the Source IP, it is expected that the return code will be received successfully and be *200*, and the **Body** contains the data defined by the API.
6. In the **Key** field of the **Request Header**, fill in *X-Forwarded-For*, and in the **Value** field, fill in the custom IP that matches the Source IP.
7. Click **Test** to view the response. Since the custom IP is defined in the Source IP, it is expected that the return code will be received successfully and be *200*, and the **Body** contains the data defined by the API.
8. In the **Key** field of the **Request Header**, fill in *X-Forwarded-For*, and in the **Value** field, fill in a random custom IP.
9. Click **Test** to view the response. Since the IP is not defined in the Source IP, it is expected that the call will fail, the return code received will be *401*, and the **Body** will respond "*`Missing srcUrl information`*".
---
# 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.tpi.dev/most-common-use-cases/api-ip-diversion.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.