> For the complete documentation index, see [llms.txt](https://docs.coda.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coda.co/https-coda-payments.gitbook.io-zhong-wen-coda-private-technical-documentation/codapay/tokenization-api-2.0/ji-cheng-zhi-nan/bai-ming-dan-ip-di-zhi.md).

# 白名单IP地址

将您的 IP 地址列入白名单

在进行 **接入和测试** 之前，请先将您的 **IP 地址** 提供给Codapay 技术支持。

您可以通过以下方式提交您的 **服务器 IP 地址**：

1. 在沟通群组中分享。
2. 通过电子邮件发送至 📧 <codapay_integration@coda.co>。

**为什么需要白名单 IP？**

* 确保您能够成功调用 **沙盒 API URL** 及访问 **沙盒** **API 端点** 进行测试。

请确保 **提交的 IP 地址是您的服务器调用 API 的固定 IP**，以免访问受限。

🙏 **感谢您的配合！**


---

# 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.coda.co/https-coda-payments.gitbook.io-zhong-wen-coda-private-technical-documentation/codapay/tokenization-api-2.0/ji-cheng-zhi-nan/bai-ming-dan-ip-di-zhi.md?ask=<question>&goal=<user_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.