> For the complete documentation index, see [llms.txt](https://docs.twosided.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.twosided.io/setting-up-your-stripe-api-key.md).

# Setting up your Stripe API key

The twosided platform requires a Stripe Secret API key in order to fully operate. You can use the Stripe integration using the account connection only, however you will have to deal with missing data:

* No personal data of suppliers and customers (only placeholders & customer IDs)
* Multi-split payments can't be supported
* No insights into aggregate supplier and customer locations

As this makes the twosided integration less effective, we recommend supplying an API key, or alternatively looking into substituting this information through our [REST API](/api-reference.md).

### Setting up a restricted key

Stripe allows you to set up a restricted key in their [developer section](https://dashboard.stripe.com/apikeys).

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

It can be a good option to give looser restrictions to this key, to avoid breaking any integration when the twosided platform updates. At a high-level, we require the following permissions:

* All core resources – Read
* All core resources (Connect permissions) – Read
* All Connect resources – Read

You can restrict the key further to only allow for required resources to be accessible. However, note that this can lead to issues with platform updates later on.

<details>

<summary>All required resources (Detailed, Latest)</summary>

* Balance transaction sources (Permissions & Connect Permissions) – Read
* Balance Transfers (Permissions & Connect Permissions) – Read
* Charges (Permissions & Connect Permissions) – Read
* Customers (Permissions & Connect Permissions) – Read
* PaymentIntents (Permissions & Connect Permissions) – Read
* Products (Permissions & Connect Permissions) – Read
* All Connect resources – Read

</details>


---

# 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://docs.twosided.io/setting-up-your-stripe-api-key.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.