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

# API keys

API credentials are managed from **Merchant Dashboard → Developers → API Keys & Webhooks**.

Enabling Business API generates both credentials at the same time:

| Credential | Purpose                                                                                       |
| ---------- | --------------------------------------------------------------------------------------------- |
| Public key | Identifies your integration and may be used in client-side products when explicitly supported |
| Secret key | Authenticates server-to-server API requests                                                   |

Secret keys begin with `PSN_sk_`. Treat them like passwords.

{% hint style="danger" %}
Never embed a secret key in browser JavaScript, a mobile application, a public repository, screenshots, or support messages.
{% endhint %}

## Resetting keys

Resetting credentials invalidates the previous key pair. Update the secret in your server environment before switching production traffic.

```bash
PAYSTATION_SECRET_KEY=PSN_sk_replace_with_your_key
```


---

# 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.paystation.ng/getting-started/api-keys.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.