Resend
Collect API-key and verified-domain inventory as read-only 'who can send as us' access-review evidence through the Resend API. Scoped strictly to access evidence, not campaign or contact data. Resend's public API does not document a team-member/role-listing endpoint as of this writing, so 'who has admin' evidence is NOT covered -- track it manually until Resend documents one.
What this connector audits
Checks this connector runs once it's connected. This is the full list; we don't claim coverage beyond what's implemented.
- API key inventory (read-only)
- Verified sending-domain inventory
- Team-member/admin-role evidence NOT covered (no documented endpoint) -- track manually
Endpoints this template queries
The exact Resend API endpoints called once connected. All read-only GET requests unless noted.
- GET/api-keys
- GET/domains
What we need
Field labels only. We never show secret values here. Credentials are encrypted at rest and used only to run the checks above.
- Base URL(prefilled: https://api.resend.com)
- Endpoints (JSON)(prefilled: [ { "id": "api-keys", "name": "API keys", "path": "/api-keys" }, { "id": "domains", "name": "Domains", "path": "/domains" } ])
- Auth header name(prefilled: Authorization)
- Auth header value(secret credential)
Required
Optional
Which frameworks this evidence supports
Resend evidence feeds into controls for any framework you run that requires this check type; the same synced evidence can satisfy more than one framework's requirements instead of being collected per audit.
Don't see your system?
Tell us what you use and what it needs to prove. We'll follow up about adding a connector.
Wire in Resend evidence
Get a guided demo, or start by scanning any domain for free.