Runs examples for real against your account. Test keys only; kept in this tab, never stored on our side. Get a key
ZapSMTP / Docs / Inbound setup

Resend the confirmation

POST/v1/inbound/forward-destinations/{id}/resend

Email a new confirmation link (the previous one stops working).

Requires a full-access live key; test keys get 403 test_key_restricted.

Path parameters

idstring
Forward destination id.

Errors

restricted_api_keyHTTP 403
test_key_restrictedHTTP 403
test-mode keys can send test email and read, not change the account: use a live key
not_foundHTTP 404
no unconfirmed forward destination with this id
rate_limit_exceededHTTP 429
a confirmation email was sent less than a minute ago
service_unavailableHTTP 503
the confirmation email could not be sent; try again
POST/v1/inbound/forward-destinations/{id}/resend
curl -X POST 'https://zapsmtp.xyz/v1/inbound/forward-destinations/019a1c55-0d6e-7f21-8b3a-5e9d4c7b2a10/resend' \
  -H "Authorization: Bearer $ZAP_API_KEY"
Set ZAP_API_KEY in your environment.
Response 200 OK
{
  "id": "0199f0b2-0000-7000-8000-00000000f001",
  "email": "team@acme.com",
  "confirmation_sent_at": "2026-10-25T10:00:00Z",
  "verified_at": null,
  "created_at": "2026-10-25T10:00:00Z"
}