> 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/changelog/2024-codapay-changelog/2024-05-17-new-parameters-added-to-codapay-api.md).

# \[2024/05/17] New Parameters Added to Codapay API

We're excited to announce that we've recently deployed two additional parameters in the Codapay Init API:

1. **in\_frame\_redirect**: This parameter allows for in-frame redirection of the merchant's complete URL.
2. **return\_url**: This parameter specifies the return URL for redirection after the payment process. 

For further information on its implementation, please refer to [Here](https://coda-payments.gitbook.io/coda-private-technical-documentation/codapay/hosted-payment-page-integration/initiate-a-payment-request#profile). (Profile Section)

These additions aim to enhance the functionality and flexibility of our API, providing you with more options to customize your integration. If you have any questions or need assistance, don't hesitate to reach out to our support team.


---

# 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/changelog/2024-codapay-changelog/2024-05-17-new-parameters-added-to-codapay-api.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.