Orvelt
Guides

Deliver verified opinion invitations

Create customer links, email invitations, and project QR codes that add provenance to an opinion.

Use preverified links when your checkout, order system, or customer-success workflow needs to invite a known customer. Use a project QR code when many customers need a reusable scan-to-opinion entry point.

Address one customer and project

Call preverifiedLinks.create with a customer email. You can add a reference and a validity window.

  • customerEmail is required and normalized.
  • customerReference is optional and limited to 255 characters.
  • validityMinutes defaults to 10080 (7 days) and accepts whole minutes from 1 through 43200.

Treat the returned URL as a bearer link. Send it only to the intended customer, and do not put customer details in a URL that you build yourself.

Email an invitation

Call preverifiedLinks.sendEmail in either of two ways:

  • Pass customerEmail and an optional customerReference to create and email a new 7-day link.
  • Pass verificationId to email an existing, unexpired link.

Orvelt limits each project to one delivery-link email per customer every 48 hours. A blocked request returns 429 with nextEligibleAt. Creating a link without emailing it does not start this cooldown.

Filter by delivery status

Use preverifiedLinks.list to page through links. Filter by status with issued, clicked, submitted, or expired; use all for the complete list.

A link becomes clicked when it is attached to a draft and submitted when that draft is completed. A completed opinion carries the delivery_link verification type.

Share a QR code

Choose permanent or rotating provenance

The Business dashboard supports two project-specific QR verification methods:

  • Permanent QR has no time-based expiry. Regenerating or revoking it invalidates existing copies for future drafts.
  • Rotating QR changes every five minutes and allows a short grace period after each refresh.

When a valid QR credential is attached to a draft, Orvelt records qr_permanent or qr_rotating as the verification type. This proves access to that project’s displayed code; it does not prove identity, purchase, or physical location.

API-key integrations can list and create QR credentials, and display the current rotating credential, with the qrCodes permission. Regenerating or revoking a code requires a Business dashboard session. See Share a verified opinion QR code for dashboard instructions.

Delivery checklist

  1. Choose an addressed link for one known customer or a QR code for a reusable display.
  2. Keep bearer links and QR credentials out of logs, analytics parameters, and message previews where possible.
  3. Save a returned verification ID only when your system needs to reconcile delivery status.
  4. Stop sending a link after it is submitted or expired.
  5. Regenerate or revoke a QR code when its displayed copies should stop verifying new drafts.