> 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/codashop-yu-distrubution/ji-cheng-zhi-nan/api-fa-bu-zhi-sheng-chan-huan-jing.md).

# API 发布至生产环境

如果所有 API 测试结果均令人满意，请根据需要将验证/顶部 URL 更新为生产环境 URL。然后您可以点击“**Push to Production**”

<figure><img src="https://3296345926-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrtIMNO1E8C0Uq9wMQU8c%2Fuploads%2FLaLx0epIxeFCjd2hR53G%2Fimage%20(20)%20copy%20(1).png?alt=media&amp;token=2c158057-15ee-40c3-b356-46e8ee98f4a2" alt=""><figcaption></figcaption></figure>

一旦您点击“Push to Production”，将会看到凭据页面。请确保提交的凭据适用于生产环境。请检查所有详细信息并点击“**提交**”，以使您的集成生效。


---

# 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/codashop-yu-distrubution/ji-cheng-zhi-nan/api-fa-bu-zhi-sheng-chan-huan-jing.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.