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

# How to Get API Keys

Keys link your system to a specific project in Trybit: they let the service know who sent a request, and let you know that a notification was actually sent by Trybit. Each project has its own set of keys.

### How to get the keys

1. **Sign up** [in the Trybit dashboard](https://app.trybit.com/login?redirect=/\&lang=en).
2. **Add a project** in the "Add project" section: select the project type, complete the "About the project" step and pass "Verification".
3. **Select an integration method** at the "Integration and API" step.
4. **Copy the keys** at the "Keys and test payments" step — this is where the API KEY, SHOP ID and SECRET KEY are issued.

<figure><img src="https://2473321126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZfSqUVTfJsB2NyMKnhq9%2Fuploads%2FsNkxe4WfamIdy1lfirU4%2F%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%202026-10-15%20%D0%B2%2014.11.38.png?alt=media&amp;token=27475f41-a578-4ca9-a2c9-c89337ddad6d" alt=""><figcaption></figcaption></figure>

After the project is created, the keys are always available in the project page header: "My projects" → the relevant project. The SECRET KEY is hidden — to view it, click "Show".

<figure><img src="https://2473321126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZfSqUVTfJsB2NyMKnhq9%2Fuploads%2Fp6XXrGZ8DUWQNx24DwKw%2F%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%202026-10-15%20%D0%B2%2018.23.47.png?alt=media&amp;token=711fe2df-67ff-4586-9cd5-a1240e3f36f9" alt="" width="563"><figcaption></figcaption></figure>

### Which keys are needed and where they are used

| **Key**    | **Purpose**                         | **Where it is used**                                                                                                                                 |
| ---------- | ----------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
| API KEY    | Authorizing API requests            | The Authorization header of every request: Token \<API KEY> — see R[equest Authorization](https://docs.trybit.com/api-reference-v2/authorization.md) |
| SHOP ID    | Project identifier                  | The shop\_id parameter when [creating an invoice](https://docs.trybit.com/api-reference-v2/create-invoice.md), HTML widget code, CMS module settings |
| SECRET KEY | Verifying notification authenticity | Verifying the JWT in a [POSTBACK](https://docs.trybit.com/api-reference-v2/postback.md)                                                              |

### Settings that can be changed only in test mode

All parameters of the "Integration and API" section — integration method, success payment URL, failure payment URL, notification URL and POSTBACK format — can be changed only while test mode is enabled. After exiting it, the section is locked; to make changes, re-enable test mode, and the project will be sent for review again.

### How to store the keys

* Store keys on the server — in environment variables or a secure configuration store.
* Do not place the API KEY and SECRET KEY in page code, mobile apps or public repositories.
* Do not share keys with third parties, including in support requests — the SHOP ID is sufficient for diagnostics.
* Restrict employee access to project settings — see [Team and Access](https://support.trybit.com/).

### What to do if a key is compromised

1. Enable test mode in the current project and add a new project in the "Add project" section — new keys are issued at the "Keys and test payments" step. The keys of an existing project cannot be changed.
2. Replace the API KEY, SHOP ID and SECRET KEY in the integration on your side, test it and submit a request to exit test mode for the new project.
3. Review recent operations in the "Payments" and "Withdrawals" sections.
4. Make sure [two-factor authentication](https://support.trybit.com/security/2fa) is enabled for the account.

{% hint style="success" %}
If you have any questions or need assistance, contact our support chat on the website and in the dashboard, or reach us on Telegram. Support contacts are listed on our [website](https://trybit.com/support).
{% endhint %}


---

# 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.trybit.com/start/get-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.
