> For the complete documentation index, see [llms.txt](https://docs.aquanow.io/pay/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aquanow.io/pay/integration-guide/web-portal.md).

# Staging Environment

We provide a dedicated staging environment for testing and development purposes. The staging environment is a separate instance of our platform, designed to mimic the production environment as closely as possible. This allows you to test your integrations, experiment with new features, and validate changes before deploying them to the live production environment.

### Accessing the Staging Environment

To obtain login credentials to our staging environment, please contact <support@aquanow.com>.

To access the client portal in staging, please visit <https://trade-staging.aquanow.io/pay>.

To use the API endpoints in the staging environment, you will need to generate separate API keys. These API keys can be generated from the client portal.

Instructions for generating API keys are available in the [API Keys](/pay/integration-guide/api-setup.md) section of the documentation.

### API Base URL

In staging , please use the following API path `https://api-staging.aquanow.io`  instead of `https://api.aquanow.io`.


---

# 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.aquanow.io/pay/integration-guide/web-portal.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.