Documentation menu

Peek Pro

Every Peek Pro booking can send the guest your liability waiver before the activity, today through Zapier or Make, with a native integration on the list.

Planned. Planned, not built. Peek's API access is through its partner programme, which we have not yet joined. Until then the automation route and the counter tablet cover it. Links go by email. They go by text only to a guest whose consent to receive texts from you is on file in SignSealer: a booking system knowing a phone number is not that guest agreeing to be texted, and SignSealer never treats it as if it were.

Today, step by step

  1. In Zapier, start from a Peek Pro new-booking trigger.
  2. Add SignSealer's Add or Update a Reservation, kind Activity.
  3. Put the SignSealer tablet app at the counter for walk-ups.

At the counter

Walk-ups sign on SignSealer's tablet app, from the form itself or a signing code, and appear in the same list as online bookings. See Tablets and kiosks.

What the native integration will do

Read bookings through Peek's partner programme and send each guest the waiver for that activity.

With the API directly

PUT https://api.signsealer.com/v1/subjects
Authorization: Bearer mk_live_…

{ "provider": "peek", "external_id": "…", "starts_on": "2026-10-10",
  "participants": [{ "ref": "…", "full_name": "…", "email": "…", "is_primary": true }] }

POST https://api.signsealer.com/v1/packets/{packet_id}/start

Keyed on the Peek Pro ID, so sending the same record twice is one reservation, and starting again sends nothing already sent. See Reservations and packets and Webhooks for the signature coming back.

Texting and consent

Signing links go by email. They also go by text only when SignSealer holds that guest's consent to receive texts from your business, recorded with the exact words they agreed to — at your counter, on your booking form through POST /v1/sms-consents, or on SignSealer's own opt-in. That check runs when the link is queued (app.may_text), not in the integration.

No booking system can give SignSealer that consent, so none is treated as if it could. Each adapter records what the provider's data said — VERIFIED_CONSENT, NO_CONSENT or INSUFFICIENT_EVIDENCE — and only NO_CONSENT changes anything: the guest's number is not written at all. Every provider built so far can only ever say INSUFFICIENT_EVIDENCE. The connection's activity shows, for each guest with a number, whether the link was also texted and why not.

How to record consent you took yourself.

Ready to build? An API key takes a minute in the portal, and the free plan covers the first 25 agreements a month.

Get an API key