Send a verification invite
When you start a verification, the console queues a branded invite automatically. This page covers resending, customizing, and tracking it.
Send the invite email
Section titled “Send the invite email”The first invite is sent inline with verification creation. The message is composed from the workflow template’s messaging.invite copy, branded with the snapshot’s effective branding, and queued after the verification record is written. A failed send never removes the verification.
The applicant receives a greeting, a CTA button that opens their invite link, and an expiry line.
Automatic reminders
Section titled “Automatic reminders”If an applicant is invited by email but does not finish, Checktiv can send automatic follow-up reminders on a cadence you choose. Reminders only go to applicants who still have a step to complete: as soon as the applicant finishes their part, or the verification moves to review, expires, or is canceled, reminders stop on their own. For a verification started from a connected reservation, reminders also stop when the reservation’s guest changes after the applicant started.
Reminders are an organization-wide setting. They apply to every verification created with the email invite enabled, whether you create it from the console, the API, a bulk CSV import, or a connected integration. An applicant you reach only by sharing the link directly is never reminded, because there is no invited email on file.
Turn reminders on
Section titled “Turn reminders on”Go to Settings, open your Organization page, and find the Applicant reminders section. Switch reminders on and choose a cadence:
- One reminder after 2 days - a single gentle follow-up.
- Two reminders, about 1 day and 2 days after invite - the default.
- Three reminders, starting about half a day after invite - the most active cadence.
The choice applies to all of your verifications at once; there is no per-verification or per-workflow-template override.
How the schedule behaves
Section titled “How the schedule behaves”- The times above are measured from your latest contact with the applicant, starting with the invite. A manual Re-send invite resets that clock, so the next reminder moves out instead of stacking on top of it.
POST /v1/sessions/{id}/resendandPOST /v1/sessions/{id}/reset_and_resenddo not reset that clock, so a reminder can arrive soon after one of them. A verification that only these calls have emailed is not reminded.- Reminders stop once the verification itself has expired (they are never sent past the verification’s own deadline).
- Every reminder gives the applicant a working link: if their invite link has lapsed, the reminder refreshes it automatically, so they never land on a dead link.
- Reminders show up in the applicant’s activity feed and the Email log, next to the original invite.
Copy the invite link
Section titled “Copy the invite link”On the new applicant response panel and on the applicant’s detail page, the applicant URL is shown alongside a QR code. The link points at the verify app’s /v/<code>?o=<otl> resolver; see How an invite link works for what the applicant has to do.
Share the link through any channel you trust. The link is single-use, so the first human click consumes it; see troubleshooting below if a resend lands on “link expired”.
Customize the invite message
Section titled “Customize the invite message”You can customize invite copy at two levels:
- Per-workflow-template (durable). Edit the workflow template’s invite subject and body in the workflow template editor. An invite uses the invite copy that the workflow template has when the verification is created or the invite is sent. See Create a workflow template.
- Per-send (one-off). The new applicant form has optional “Customize invite email” fields that override the workflow template copy for one send.
When per-send fields are blank, the send falls back to the workflow template’s messaging.invite. When the workflow template has none, it falls back to the platform default copy.
The API uses the invite copy of the workflow template when you create a verification with send_invite: true. It also uses that copy when you call POST /v1/sessions/{id}/resend or POST /v1/sessions/{id}/reset_and_resend. When Checktiv sends an invite for a verification that a connected system started, it uses the same copy. A verification that you create with checks instead of a workflow template gets the platform default copy.
A blank line in the message starts a new paragraph. A single line break inside a paragraph is shown as a space.
Resend or revoke
Section titled “Resend or revoke”Open the applicant’s detail page and click Send invite (Re-send invite once an invite has been sent or attempted). The endpoint:
- Re-derives the recipient by decrypting the stored email envelope. You cannot pass a different address.
- Reuses the existing invite link only while it is unused, unexpired, and the applicant link it opens lasts at least as long as it. Otherwise it generates a fresh one inline, which also renews the applicant link for the workflow’s link lifetime, up to the verification’s deadline. Sending an invite never extends that deadline.
- Refuses the send if the verification has already reached
completed,awaiting_review,processing,expired, orcancelled(session_finished). - Refuses the send while the verification is paused because the account balance could not pay for its next check (
session_parked). The message names the next step: add funds in Billing, or follow the steps there for a frozen or locked wallet. The verification then resumes automatically, and you can send the invite. See Payment required for the one paused verification that does not resume. - Refuses the send once the applicant can no longer finish the verification, for example because it is past its deadline (
session_past_deadline). Start a new verification for them. A verification from a reservation in a connected system is also refused once the reservation’s due time has passed, and the applicant’s detail page then shows the reservation’s next step. Through the API,POST /v1/sessions/{id}/resendandPOST /v1/sessions/{id}/reset_and_resendrefuse both with409 session_already_completed, and the message names the next step.
Two anti-spam guards apply to Send invite in the console:
- Cooldown. A resend within 60 seconds of the previous send is rejected as
rate_limited. - Daily cap. Five invite attempts per verification in any rolling 24 hours, counting the first invite, whether or not each was delivered. A send over the cap is also rejected as
rate_limited, and its message says the limit lifts as those attempts pass 24 hours old. In the meantime, if the detail page shows the link, copy it or its QR code and share it directly; if the link was already used or has expired, generate a new link first.
Three API requests share one invite limit: POST /v1/sessions with send_invite: true, POST /v1/sessions/{id}/resend, and POST /v1/sessions/{id}/reset_and_resend. Your organization can send at most three invite emails in an hour to one email address through them. The limit counts the invite that creation sends. For these requests, test mode and live mode share one count. Send invite in the console and the CSV import use their own limits.
Checktiv refuses the next resend or reset_and_resend request with 429 rate_limit_exceeded. If you send an Idempotency-Key, use a new key when you retry after details.reset_at, because Checktiv replays the stored refusal for the old key. A creation with send_invite: true over the limit still succeeds and sends no invite, and the response does not say so. Deliver applicant_url from the response, send the invite from the applicant’s detail page, or call resend after an hour. A refused reset_and_resend also does not rotate the link or reset progress. Rotating the link replaces the single-use link and the client_token. For a verification from a reservation in a connected system, it does not stop the reservation’s own link. To stop that link, cancel the verification. If the applicant’s detail page says the link was already used or has expired, Generate new link on that page rotates it immediately. While the page shows the link to copy, the console offers no rotation. Retry reset_and_resend after the time in details.reset_at. To replace that link before then, call POST /v1/sessions/{id}/regenerate_link. It issues a new single-use link without an email and keeps the client_token. See Per-recipient invite limit.
The email that resend or reset_and_resend sends is the invite email, but the console does not count it as the invite. After one of these calls, the invite status line and the Send invite button label do not change. The button label stays Send invite until an invite is sent from another source. Examples are creation with send_invite: true and Send invite in the console.
To revoke an outstanding invite, cancel the verification (which finishes it and rejects further sends). To invalidate an unopened link without canceling, call POST /v1/sessions/{id}/regenerate_link. It issues a new single-use link, so the earlier link stops working, and it sends no email. The applicant’s detail page has no control for this while it shows the link to copy. If the link was already opened, the device that opened it stays signed in. Generate new link on the applicant’s detail page signs that device out, and so does canceling the verification.
Check the email log
Section titled “Check the email log”Delivery signals are surfaced on the applicant’s detail page and in the activity feed. A dedicated Email log lists outbound emails with their recipient, subject, status, and timestamp.
Troubleshooting
Section titled “Troubleshooting”- “Link expired” on first click. The invite link is valid for 72 hours from issue by default (see How long links last). Ask the applicant to self-service on the expired page, or resend.
- Email never arrives. Check the activity feed for Verification invite emailed. After a resend in the console, look for Verification invite re-sent. After an API
resendorreset_and_resend, look for Applicant link re-sent or Applicant link reset and re-sent. If one is present, ask the applicant to check spam. no_recipienton resend. The verification has no email address on file. Cancel and recreate with one, or copy the link from the applicant’s detail page and share it directly. If that link was already used or has expired, generate a new link first. Through the API,POST /v1/sessions/{id}/resendrefuses the same verification with422 validation_error. CallPOST /v1/sessions/{id}/regenerate_linkinstead: it returns a new link for you to deliver, with no email. See Get a new link by API.- Reminders not going out. Automatic reminders only apply when they are switched on in Settings > Organization > Applicant reminders, the verification was invited by email, and the applicant has not finished yet. They also stop once the verification itself has expired.