Resend
Probo reads your Resend account’s API keys through the Resend API so you can review which programmatic credentials have access.
Prerequisites
Section titled “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
Section titled “Collected Fields”Resend exposes the account’s API keys rather than human members, so each reviewed account is an API key (a service account).
| Probo field | Resend field | Notes |
|---|---|---|
| Name | name | The label given to the API key when it was created |
| Not supported | ||
| Role | Not supported | |
| Admin | Not supported | |
| Status | Not supported | |
| MFA | Not supported | |
| 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
Section titled “Step 1: Create an API Key”
- In the Resend dashboard, go to API Keys in the sidebar.
- 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. - Copy the key (
re_…) and store it securely. It is shown only once.
Step 2: Connect in Probo
Section titled “Step 2: Connect in Probo”- In Probo, go to Access Reviews > Sources > Add Source.
- 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
Section titled “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.