> 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://app.staging.aquanow.com/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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.aquanow.io/pay/integration-guide/web-portal.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.