Resend a sender confirmation
Mails a fresh confirmation link to a pending address a workspace person has already approved, and invalidates the previous one.
This emails a real person, so send an Idempotency-Key and do not loop on it. Only a pending grant can be resent to: an active one answers 409 invalid_state, because re-issuing would drop it back to pending. A grant with awaitingApproval: true answers 403 forbidden: a credential cannot send the first link, because sending it is the approval, and only a workspace owner or admin can give that from the dashboard.
Request
- Base URL: https://inkseal.net/api/v1
- URL: https://inkseal.net/api/v1/account/authorized-senders/{senderId}/resend-confirmation
- Auth: HTTP bearer
Headers
Makes this mutation retry-safe. 1 to 255 printable ASCII characters (0x20 to 0x7e), trimmed before use. The key is scoped to the workspace and the credential that sent it. Reusing it with a different method, path, or payload answers 422 idempotency_key_reuse. A completed attempt replays its stored status and body with an Idempotent-Replay: true response header; 5xx, 429, and non-JSON answers leave the key retryable. A concurrent request holding the 90 second lease answers 409 idempotency_in_progress. Records are retained 24 hours.
Response
The grant, still pending, and whether the confirmation email went out.
Example response
{
"data": {
"sender": {
"id": "Sn4kR7pQx2LmVb9tY6cZw",
"email": "contracts@example.com",
"kind": "delegate",
"status": "pending",
"confirmationSentAt": "2026-08-21T09:14:02.000Z",
"expiresAt": "2026-08-28T09:14:02.000Z",
"createdAt": "2026-08-21T09:14:02.000Z",
"updatedAt": "2026-08-21T09:14:02.000Z"
},
"confirmationEmailSent": true
}
}Changes
No recorded changes to this operation across all 1 revision of this API.