# Resend

Probo reads your Resend account's API keys through the Resend API so you can review which programmatic credentials have access. It does not collect the people on your Resend team, because the Resend API does not expose them.

:::caution
Use a **Full access** API key (`re_…`) created in the Resend dashboard. A **Sending access** key (also prefixed `re_…`) will **not** work, because it can only send emails and cannot read your account's API keys.
:::

## Prerequisites

- Probo organization administrator access
- Access to the Resend account's **API Keys** page, so you can create the key for the account you want to review
- A Resend API key with **Full access** (Sending access cannot read the account's API keys)

## Collected Fields

The Resend dashboard lists your team members under **Settings** > **Team**, but the public API has no endpoint that returns them, so Probo cannot collect them. Resend exposes the account's API keys instead, so each reviewed account is an API key (a service account) with no email or role, and no account is flagged admin. To review the people on your Resend team, add them through a [CSV source](/docs/product/access-review/csv-sources).

The Full access key used to connect Probo is part of the same API-key inventory and can therefore appear in the campaign. Review it like any other privileged programmatic credential.

| Probo field | Resend field                                             | Notes                                                      |
| ----------- | -------------------------------------------------------- | ---------------------------------------------------------- |
| Name        | `name`                                                   | The label given to the API key when it was created         |
| Email       |  |                                                            |
| Role        |  |                                                            |
| Admin       |  |                                                            |
| Status      |  |                                                            |
| MFA         |  |                                                            |
| Last login  | `last_used_at`                                           | When the API key was last used to call the Resend API      |
| External ID | `id`                                                     | Stable identifier used to track the API key across reviews |
| Created at  | `created_at`                                             | When the API key was created                               |

## Step 1: Create an API Key

![Creating a Full access API key in the Resend dashboard](/docs/access-review/resend-create-api-key.webp)

1. In the [Resend dashboard](https://resend.com/api-keys), go to **API Keys** in the sidebar.
2. Click **Create API Key**, name it (e.g. `Probo Access Review`), and set **Permission** to **Full access**, since Probo needs to read the account's API keys.
3. Copy the key (`re_…`) and store it securely. It is shown only once.

## Step 2: Connect in Probo

1. In Probo, go to **Access Reviews** > **Sources** > **Add Source**.
2. Find **Resend**, click **API Key**, paste the key, and click **Connect**.

Probo lists the source as **Resend** and pulls the account's API keys into your campaigns.

## Troubleshooting

- **Key rejected.** Confirm it is a **Full access** key (`re_…`). A Sending access key only sends emails and will not connect.
- **No API keys appear.** The key must have **Full access** and belong to the Resend account you are reviewing.
- **Team members do not appear.** The Resend API returns no team members, so this source only ever contains API keys. Review the people on your team from **Settings** > **Team** in the Resend dashboard, and track them in Probo with a [CSV source](/docs/product/access-review/csv-sources).