Integrations

An integration connects one of your existing systems to Checktiv so that identity verification starts on its own. When the connected system creates a new record, such as a reservation, Checktiv receives it, starts a verification, and can invite the person to complete it, all without anyone opening the console. You manage integrations from Dashboard → Integrations.

When to use integrations

Use an integration when the event that should trigger a verification already happens in another tool you run. Instead of exporting a list and starting verifications by hand, or building against the API yourself, you connect the system once and every new record it creates starts a verification automatically.

This suits teams that:

• Take new bookings, reservations, or customer records in a system Checktiv can connect to, and want each one verified.
• Prefer a no-code setup over writing against the REST API.
• Want a consistent set of checks applied to everyone, without depending on staff to remember to start each verification.

If you only need to verify a handful of people, or want to script the flow yourself, start a verification directly or use the API instead.

How it works

Once you connect a system, Checktiv registers to receive its new-record notifications. From there each new record flows through automatically:

1. The connected system creates a new record (for example, a new reservation) and notifies Checktiv.

2. Checktiv reads the record, applies your routing rules, and, unless a rule tells it to skip, starts a verification bound to the connection’s default workflow.

3. If the record has already produced a verification, Checktiv reuses it rather than starting a duplicate.

4. Depending on your invitation setting, Checktiv either sends the verification invitation itself or leaves that to the source system.

Each verification an integration starts appears in your Applicants list alongside verifications you start any other way, and runs the same checks and review flow.

Default workflow

Every connection binds to one default workflow, which is required. It is the workflow template that every verification from this connection runs, so it decides which checks each person goes through.

You choose the default workflow when you connect a system, and you can change it later by editing the connection. You cannot connect a system until you have at least one workflow template to bind, so create a workflow template first if you have none.

Tip

Give each connection the workflow that matches the people it verifies. If different systems need different checks, connect them separately and bind each to its own default workflow.

Routing rules

By default, every new record from a connected system starts a verification. Routing rules let you narrow that down so only the records you want are verified.

A routing rule matches records on a field and, when it matches, skips them. You can match on:

• The reservation or booking source.
• The property or listing identifier.
• The external record identifier.
• The check-in date.
• The check-out date.

Each rule holds a list of values to match against, and a record is skipped when its field exactly equals one of those values. A common use is to exclude records that arrive from a channel you do not want to verify. Matching is exact: there are no wildcards or partial matches.

Rules are evaluated in order, and the first rule that matches decides the outcome. A record that no rule matches is verified as normal. You can add several rules per connection to cover multiple exclusions.

Note

A rule with no values entered never matches, so add at least one value or it has no effect. Leave the routing rules empty to verify every record.

Sending verification invitations

When a verification starts from an integration, someone needs to receive the link to complete it. The Send verification invitations setting controls who sends it.

• On (the default): Checktiv sends the verification invitation to the person automatically as soon as the verification starts. This is the out-of-the-box behavior, so a newly connected system invites people with no extra setup.
• Off: Checktiv does not send the invitation. The verification still starts, but the source system is responsible for inviting the person, using the verification link that Checktiv writes back to that system. Turn this off only when the source system is set up to deliver that link, otherwise the person will not receive it.

You set this per connection when you connect or edit a system.

Managing a connection

Connected integrations are listed under Dashboard → Integrations. From there you can:

• Connect a system from the catalog below by entering its credentials, choosing a default workflow, setting routing rules, and confirming the invitation setting.
• Edit a connection to change its default workflow, routing rules, or invitation setting. You can leave the credentials blank when editing to keep the ones already stored.
• Reconnect a connection whose credentials have stopped working. Checktiv flags a connection as needing reconnection when it can no longer reach the system; reconnecting prompts you for fresh credentials.
• Pause a connection to stop it starting new verifications while keeping it configured, then Resume it later to start again. A paused connection ignores new records until you resume it.
• Disconnect a connection to remove it. This stops new verifications from the system and is confirmed before it takes effect. Verifications that already started are unaffected.

Caution

Pausing and disconnecting only stop future verifications. Verifications already in progress continue through their checks and review as usual.

Available integrations

Hostaway is available to connect today. Additional integrations across property management, payments, and business apps appear in the catalog as they become available.

HostawayStart a verification automatically when a new reservation is created in Hostaway.