# Integrations

A booking system sends SignSealer each reservation; the documents you chose for it decide what each guest signs; the guest is sent it. Nobody re-types a name, and nothing already sent is sent again.

| System | Kind | Status |
| --- | --- | --- |
| **[Guesty](https://signsealer.com/docs/integrations/guesty)** | Vacation rentals | Beta |
| **[Hostaway](https://signsealer.com/docs/integrations/hostaway)** | Vacation rentals | Beta |
| **[Hospitable](https://signsealer.com/docs/integrations/hospitable)** | Vacation rentals | Awaiting partner approval |
| **[Zapier](https://signsealer.com/docs/integrations/zapier)** | Automation | Beta |
| **[Make](https://signsealer.com/docs/integrations/make)** | Automation | Beta |
| **[Lodgify](https://signsealer.com/docs/integrations/lodgify)** | Vacation rentals | Beta |
| **[Hostfully](https://signsealer.com/docs/integrations/hostfully)** | Vacation rentals | Beta |
| **[HubSpot](https://signsealer.com/docs/integrations/hubspot)** | CRM | Planned |
| **[Zoho CRM](https://signsealer.com/docs/integrations/zoho-crm)** | CRM | Planned |
| **[Pipedrive](https://signsealer.com/docs/integrations/pipedrive)** | CRM | Planned |
| **[Salesforce](https://signsealer.com/docs/integrations/salesforce)** | CRM | Planned |
| **[Jobber](https://signsealer.com/docs/integrations/jobber)** | Field services | Planned |

**Beta** means a customer can connect it today, built against the provider's published API and tested against it on our side. **Awaiting partner approval** means it is built and the provider has to approve SignSealer before anyone can connect it. **Planned** means it cannot be connected yet. Most of those are built and wait on SignSealer's own app at the provider being approved and listed; each guide says where it has got to, and shows how to get the same result today with Zapier, Make or the API.

## The membership

Connecting a booking system comes with the membership, beside texting, passcodes, ID Evidence and white label ([pricing](https://signsealer.com/pricing)). The membership keeps the first 10 signings of each month free, however they arrive. On Free you still get 10 signings a month, sent from the dashboard. Zapier, Make and the API work on Free: they are the API, which every plan includes.

If the membership ends, each connection is paused rather than removed. It keeps recording what the provider sends, one waiting delivery per booking, and resumes by itself when the membership starts again, catching up on what changed meanwhile. A connection you paused yourself stays paused. From your own code, `GET
/v1/integrations` answers `needs_membership`, and a connection paused this way has `paused_reason: "membership"`.

## How a connection works

1. **You connect it** under [Integrations](https://app.signsealer.com/integrations) in the dashboard, with credentials you create in the provider. SignSealer checks them with the provider before keeping anything, then registers its webhook there when the provider allows that.
2. **The connection is a key.** Each connection owns an API key of its own, scoped to reservations and signing, whose secret nobody holds. Everything the integration does in your account is done as that key, through the same checks as the API, and the activity log names it. Disconnecting revokes it.
3. **The provider tells SignSealer.** Each connection has its own delivery address. A delivery is proven to be the provider's before anything in it is read — by signature where the provider signs, otherwise by the address's secret plus reading the booking back from the provider's API.
4. **The booking becomes a reservation.** A worker reads the booking as it is now, then writes the reservation, its guests and its packet, exactly as `PUT /v1/subjects` would.
5. **Its documents decide.** The documents chosen on the connection's page say what each guest owes, and the packet lists it. The connection sends it straight away or waits for you.

## What a document can print from the booking

A template sent for a booking can use these blanks, and SignSealer fills them from the record. An estimate, invoice, quote or deal that brings an amount can be accepted in so many words: *“I accept estimate {{document_number}} and agree to pay {{amount}}.”*

| Blank | What it prints | Example |
| --- | --- | --- |
| **`{{participant_name}}`** | The person signing, or the guest a guardian signs for | Dana Builder |
| **`{{activity_date}}`** | The booking's day, or the record's date | October 2, 2026 |
| **`{{amount}}`** | The total, as money | $4,250.00, or 980.00 EUR |
| **`{{amount_due}}`** | What is still owed, when the record says; otherwise the total | $450.00 |
| **`{{currency}}`** | The currency's code | USD |
| **`{{document_number}}`** | The estimate's, invoice's or quote's own number | 1042 |
| **`{{due_date}}`** | When an invoice is due | October 15, 2026 |
| **`{{expiry_date}}`** | When an estimate or quote runs out | November 1, 2026 |

A blank is filled only when the record has it. A template that prints `{{amount}}` is not sent for a record with no amount; the packet says which blank was missing. These are blanks, not the provider's own invoice: the signer reads your template's words with the record's figures in them.

## Secrets

A connection's credentials, the provider's webhook secret, the access token SignSealer was issued and the delivery address's token are sealed together with the same key that seals every other credential, and are never shown again after you enter them. The address token is kept as a hash for lookup; somebody who can manage the connection can read the address again, for when it has to be entered in the provider by hand.

## 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](https://signsealer.com/docs/texting).

## Settings

| Setting | Choices | What it does |
| --- | --- | --- |
| **When a booking arrives** | Send straight away (default) · Build the list and wait | Straight away starts everything the packet owes as soon as the booking is worked. Waiting builds the reservation and its packet and sends nothing until somebody presses Send on the reservation, or your code calls `POST /v1/packets/{id}/start`. |
| **When a booking is canceled** | Void what nobody has signed (default) · Leave it | Voiding marks every unfinished document with the reason and the packet void. Anything already signed is kept: an executed waiver is evidence of what was agreed. |

What each guest is sent is decided by the connection's **documents for bookings**, chosen on its page: each says which document, who signs it — the person who booked, every adult, or a parent or guardian for each minor — and which bookings, read from the reservation's facts (dates, guest counts, property, channel). A default covers the bookings nothing else fits, and a booking that matched nothing says so in the connection's activity ([Reservations and packets](https://signsealer.com/docs/packets)).

## Duplicates, order and retries

- **Once.** A delivery is recorded once per connection and event id. A provider that redelivers the same event gets `200 {"duplicate": true}` and nothing happens twice.
- **Newest wins.** Each event means "read this booking as it is now". A newer event about a booking supersedes an older one still waiting, and one booking is never worked twice at once.
- **Nothing is sent twice.** Guests are recognized by their id in the provider (or by address and name), so an update keeps each guest's link to what they were already sent.
- **Retries.** A failure is retried after 1, 2, 4, 8 … minutes, up to six hours apart, and gives up after eight tries. It is then listed, with its reason, under the connection's activity, where it can be tried again once whatever refused it is fixed.
- **The reason is in our words.** What the activity says of a failure is one plain sentence about what happened and what to do: the provider refused our credentials, did not answer, is limiting us, answered with an error, or says the booking or listing does not exist. It carries the provider's status code where there is one, such as `(422)`, and a short reference to quote if you write to us. What the provider itself wrote back is not kept or shown, because it can quote a guest's name, email or phone.
- **Refused credentials.** If the provider refuses SignSealer's credentials, the connection goes to *needs attention* and stops working events until new credentials are given. What arrives meanwhile is kept and worked afterwards.
- **Retention.** What arrived is cleared thirty days after it was worked; the outcome and the reservation it made are kept.

## Versions and deprecation

Each provider row records the version of SignSealer's connector and the provider API version it is built against, and each connection records what it last ran with. When a provider deprecates an API version we depend on, the provider's row carries the date it is deprecated and the date it goes away, the change is written to the activity log of every business connected to it, and it shows on the Integrations screen.

## Pausing and disconnecting

**Pause** keeps recording what arrives and works nothing until you resume. **New address** stops the old delivery address at once (and re-registers the webhook with the provider where SignSealer set it up). **Disconnect** revokes the connection's key, clears its credentials, removes the webhook from the provider where it can, and closes the address. The reservations and documents it made stay, with where they came from.

## From your own code

```
curl https://api.signsealer.com/v1/integrations -H "Authorization: Bearer $KEY"
curl https://api.signsealer.com/v1/integrations/$CONNECTION/events -H "Authorization: Bearer $KEY"
```

The first lists every provider with its status and your connections with their state; the second is what arrived from one connection and what became of it. Neither ever returns a credential, a delivery address or what arrived. Both need the `signing:read` scope. Connecting happens in the dashboard, where the provider confirms the credentials. See the [API reference](https://signsealer.com/docs/api).

## Zapier, Make and your own code

Every integration here is built on the public API. Anything these pages do, your code can do with `PUT /v1/subjects`, `POST /v1/packets/{id}/start`, `POST /v1/packets/{id}/void` and [webhooks](https://signsealer.com/docs/webhooks) — [Reservations and packets](https://signsealer.com/docs/packets) walks through it.

[This page as Markdown](https://signsealer.com/docs/integrations.md) Ask an AI about it: [ChatGPT](https://chatgpt.com/?q=Please%20read%20https%3A%2F%2Fsignsealer.com%2Fdocs%2Fintegrations%20and%20explain%20it%20to%20me%20as%20a%20developer%20adding%20SignSealer%20to%20my%20application%3A%20what%20it%20covers%2C%20the%20calls%20involved%20and%20anything%20to%20watch%20out%20for.%20Use%20https%3A%2F%2Fsignsealer.com%2Fllms.txt%20for%20the%20rest%20of%20the%20docs%2C%20and%20cite%20the%20page%27s%20URL%20in%20your%20answer.) · [Claude](https://claude.ai/new?q=Please%20read%20https%3A%2F%2Fsignsealer.com%2Fdocs%2Fintegrations%20and%20explain%20it%20to%20me%20as%20a%20developer%20adding%20SignSealer%20to%20my%20application%3A%20what%20it%20covers%2C%20the%20calls%20involved%20and%20anything%20to%20watch%20out%20for.%20Use%20https%3A%2F%2Fsignsealer.com%2Fllms.txt%20for%20the%20rest%20of%20the%20docs%2C%20and%20cite%20the%20page%27s%20URL%20in%20your%20answer.) · [Perplexity](https://www.perplexity.ai/search?q=Please%20read%20https%3A%2F%2Fsignsealer.com%2Fdocs%2Fintegrations%20and%20explain%20it%20to%20me%20as%20a%20developer%20adding%20SignSealer%20to%20my%20application%3A%20what%20it%20covers%2C%20the%20calls%20involved%20and%20anything%20to%20watch%20out%20for.%20Use%20https%3A%2F%2Fsignsealer.com%2Fllms.txt%20for%20the%20rest%20of%20the%20docs%2C%20and%20cite%20the%20page%27s%20URL%20in%20your%20answer.) · [Google AI](https://www.google.com/search?udm=50&q=Please%20read%20https%3A%2F%2Fsignsealer.com%2Fdocs%2Fintegrations%20and%20explain%20it%20to%20me%20as%20a%20developer%20adding%20SignSealer%20to%20my%20application%3A%20what%20it%20covers%2C%20the%20calls%20involved%20and%20anything%20to%20watch%20out%20for.%20Use%20https%3A%2F%2Fsignsealer.com%2Fllms.txt%20for%20the%20rest%20of%20the%20docs%2C%20and%20cite%20the%20page%27s%20URL%20in%20your%20answer.) · [Grok](https://grok.com/?q=Please%20read%20https%3A%2F%2Fsignsealer.com%2Fdocs%2Fintegrations%20and%20explain%20it%20to%20me%20as%20a%20developer%20adding%20SignSealer%20to%20my%20application%3A%20what%20it%20covers%2C%20the%20calls%20involved%20and%20anything%20to%20watch%20out%20for.%20Use%20https%3A%2F%2Fsignsealer.com%2Fllms.txt%20for%20the%20rest%20of%20the%20docs%2C%20and%20cite%20the%20page%27s%20URL%20in%20your%20answer.)
