> For the complete documentation index, see [llms.txt](https://apidocs.onekeypayments.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://apidocs.onekeypayments.com/guides/getting-started/get-your-api-keys.md).

# Get your API Keys

### Environments

We will provide access to our **Staging environment** and when your integration is ready, we will grant you access to **Production environment**. \
Still, you will keep your Staging account for you to test whatever you need.

In each environment you will have your own Merchant account. Each with its own set of credentials and Merchant Panel access.

Within the Merchant Panel you will easily distinguish the environments by the page logo.

<div data-full-width="false"><figure><img src="/files/fHj0NMsC4AwCZF58TJgY" alt="" width="188"><figcaption></figcaption></figure> <figure><img src="/files/Jn4iy4PpfU0vFiXV1BmH" alt="" width="188"><figcaption></figcaption></figure></div>

#### **URLs**

<table><thead><tr><th width="144.00390625">Environment</th><th width="324.71484375">URL</th></tr></thead><tbody><tr><td>Staging</td><td><code>https://api-stg.onekeypayments.com</code></td></tr><tr><td>Production</td><td><code>https://api.onekeypayments.com</code></td></tr></tbody></table>

### API Credentials

#### **Deposits**

<table><thead><tr><th width="183.30859375">Application</th><th>Name as in the Merchant Panel</th><th>API Reference</th></tr></thead><tbody><tr><td>Deposits API</td><td>API Key</td><td><code>X-Login</code></td></tr><tr><td>Deposits API</td><td>API Signature</td><td><code>Signature</code></td></tr><tr><td>Fragments SDK</td><td>API Public Key</td><td><code>publicKey</code></td></tr><tr><td>Read Only Endpoints</td><td>Read Only API Keys</td><td></td></tr></tbody></table>

#### **Cashouts**

<table><thead><tr><th width="183.30859375">Application</th><th>Name as in the Merchant Panel</th><th>API Reference</th></tr></thead><tbody><tr><td>Cashouts API</td><td>API Key</td><td><code>login</code></td></tr><tr><td>Cashouts API</td><td>API Passphrase</td><td><code>pass</code></td></tr><tr><td>Cashouts API</td><td>API Signature</td><td><code>Payload-Signature</code></td></tr><tr><td>Read Only Endpoints</td><td>Read Only API Keys</td><td></td></tr></tbody></table>

### Retrieve your credentials

You can access and manage your API Keys within the Staging and Production Merchant Panels.

After logging in, go to ***Settings*** :arrow\_right: ***API access.***

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


---

# 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://apidocs.onekeypayments.com/guides/getting-started/get-your-api-keys.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.