> ## Documentation Index
> Fetch the complete documentation index at: https://docs.quidkey.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Set Up a Partner Account

> Get your partner credential, a token, and the merchants you hold

A partner holds one credential, which onboards its merchants and creates payment transactions for them.

| # | Step | Who |
| - | - | - |
| 1 | Quidkey gives you your `client_id` and `client_secret` | **Quidkey** |
| 2 | Exchange them for an access token | API |
| 3 | Read your own API key, to learn your partner ID | API |
| 4 | List your merchants | API |

**1. Get your credential**

Quidkey gives you your `client_id` and `client_secret`. To rotate or revoke the secret, contact Quidkey. The API doesn't manage credentials. A token issued before the secret was revoked or rotated stops working.

**2. Get an access token**

```bash theme={null}
curl -X POST 'https://api.quidkey.com/v1/oauth2/token' \
  -u 'YOUR_CLIENT_ID:YOUR_CLIENT_SECRET' \
  -H 'Content-Type: application/x-www-form-urlencoded' \
  -d 'grant_type=client_credentials'
```

```json Response theme={null}
{ "access_token": "ACCESS_TOKEN", "token_type": "Bearer", "expires_in": 900 }
```

A token lasts `expires_in` seconds. Get a new one from your credential when it expires: there's no refresh token.

**3. Learn your partner ID**

```bash theme={null}
curl 'https://api.quidkey.com/v1/api-keys/current' \
  -H 'Authorization: Bearer ACCESS_TOKEN'
```

```json Response theme={null}
{
  "result": {
    "_type": "api_key",
    "_uri": "/api-keys/key_1",
    "_view": "full",
    "id": "key_1",
    "owner": { "_type": "partner", "id": "p_1" },
    "created_at": null,
    "updated_at": null
  },
  "entities": {},
  "not_included": []
}
```

`owner` is your partner. It has no `_link`, because the API doesn't publish partners, so `?include=owner` lists it in `not_included`. Use `owner.id` in the partner routes.

**4. List your merchants**

```bash theme={null}
curl 'https://api.quidkey.com/v1/partners/p_1/merchants' \
  -H 'Authorization: Bearer ACCESS_TOKEN'
```

The answer is a [cursor-paginated list](https://docs.quidkey.com/api-v1/standards/collections.md) of `merchant` resources. Each one links to its `onboarding`, `capabilities`, `transactions`, `payouts` and the rest.

## Next

> [card] [Set up partner webhooks](https://docs.quidkey.com/api-v1/journeys/partner-webhooks.md)
>
> Receive your merchants' payment transaction and status events

> [card] [Onboard a merchant](https://docs.quidkey.com/api-v1/journeys/onboard-a-merchant.md)
>
> Create a merchant and take it live


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.