> 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/codashop-and-distribution/integration-guides/pushing-the-api-to-production.md).

# Pushing the API to Production

If all the API test results are satisfactory, please update the validate/top urls to **production urls** if needed. Then you can click on <mark style="color:purple;">**Push to Production**</mark>

<figure><img src="/files/b7Rgz8tDDsCAI9a7w4d9" alt=""><figcaption></figcaption></figure>

Once you click on Push to Production, you will see the credentials page. Make sure that the credentials you submit are for **Production environment credentials**. Please check all the details and click on <mark style="color:purple;">**Submit**</mark> to make your integration <mark style="color:green;">**LIVE**</mark>

For any queries related to integration, reach out to the [Partnership Support Team](/references/contact-us.md).


---

# 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.coda.co/codashop-and-distribution/integration-guides/pushing-the-api-to-production.md?ask=<question>&goal=<endgoal>
```

`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.
