> ## Documentation Index
> Fetch the complete documentation index at: https://readme.amana-dev.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Environments and Access
> Confirm API environments, credentials, and test arrangements before connecting your application.
Confirm environment and access details with Amana as part of partner onboarding. Do not infer an API base URL from this documentation site's domain.
## Details to Confirm
| Detail | Why it matters |
| - | - |
| API base URL | Requests must reach the environment approved for your integration. |
| Authentication flow | Partner-level and user-scoped access may have different requirements. |
| Credential scope | Access must match the accounts and operations your integration is approved to use. |
| Test environment and accounts | Development needs an agreed way to test without affecting real clients or funds. |
| Usage and network restrictions | Confirm limits, allowlists, and any other access constraints before testing. |
## Separate Environments
Keep production and non-production configuration and credentials separate. Label each environment clearly in your deployment configuration and operational tools.
Do not assume a sandbox exists or that a production credential works in a test environment. Confirm the available test arrangements before making requests.
## Protect Access Details
Use a secret-management mechanism for confidential credentials. Do not store them in source code, public documentation, browser storage, or mobile application bundles. Confirm the supported refresh, expiry, rotation, and revocation procedures for each credential type.
Production order, funding, and withdrawal requests can have real financial effects. Do not send them as exploratory tests or from interactive documentation examples.
Continue with [security considerations](/integration-guides/security).
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.