import { Aside, Steps } from '@astrojs/starlight/components';

The Streamline integration verifies the applicant of each qualifying reservation in your Streamline company automatically. You connect once, choose the workflow the verification runs and the [verification timing](/guides/integrations/verification-timing), and each qualifying reservation starts a verification for the applicant when its verification opens (by default, as soon as the integration reads it), without any manual step. The verification's status is written onto the reservation as a reservation flag, and the applicant's verification link and an internal review link are written on as internal notes, so your team sees them where they already work.

This page covers the Streamline integration specifically. For the full list of available integrations and how connections work in general, see the [Integrations overview](/guides/integrations).

<Aside type="caution" title="If you use our earlier Streamline integration, turn it off first">
  Turn off our earlier Streamline integration before you connect here. The two integrations cannot
  run together: Streamline gives both of them the same token pair, and each one renews that pair on
  its own schedule, so each renewal stops the other integration from working.
</Aside>

## When to use

Connect Streamline when you want reservations to trigger identity verification on their own, instead of adding each applicant by hand or through the API. It suits teams that:

- Take reservations in Streamline and want the applicant on every booked reservation verified before arrival.
- Want the verification status and links visible on the reservation, so reviewers and front-desk staff do not switch tools.
- Want to control which reservations get verified (for example, skip owner stays, or run some on a different workflow) with routing rules rather than code.

If you only verify applicants occasionally, or you drive verification from your own system, the [API](/reference) or a [bulk CSV import](/guides/verification/bulk-import-csv) may fit better. You can use the integration alongside either.

## How it works

The integration does not wait for Streamline to send it changes. Instead, once connected, it checks Streamline for new and updated reservations on its own schedule:

1. **The integration checks Streamline.** This happens every few minutes, so a reservation is typically picked up within about 5 minutes of being created or updated in Streamline.
2. **The reservation status decides the action.** The integration reads the reservation and acts on its status (see the table below). A booked reservation gets its verification link, and starts a verification when its verification opens if it does not already have one; a quote or a request is skipped; a canceled reservation withdraws a verification still waiting on the applicant or on your account's funds, and one already being checked or decided keeps its result.
3. **A verification is started.** For a reservation that should be verified, the integration starts a verification bound to the default workflow you chose when connecting, or to the workflow a routing rule selects for it. It starts when the reservation's verification opens. Before then, the applicant's link shows when they can start. The reservation's contact details are carried onto the applicant so reviewers can identify them in the console, and the reservation's reference is stored as the applicant's external reference.
4. **The applicant is invited, if the invite is on.** A new connection, including one you connect again after a disconnect, starts with **Send the verification invite** off. Turn it on to have the platform email the applicant their verification link; leave it off if you would rather send the link yourself from Streamline using the note described below. A connection that already exists keeps its setting, which the connection's **Edit** drawer shows.
5. **The status and links are written back.** The verification's status is kept in step on a reservation flag you create in Streamline. The verification link is written as an internal note as soon as the reservation qualifies, before any verification starts, and an internal review link is written as an internal note when the verification starts.

### What each reservation status does

The integration decides what to do from the reservation's status. This is the default behavior for a new connection:

| Streamline status                                                                                          | Console record status | What happens                                                                                                                                                                                                                 |
| ---------------------------------------------------------------------------------------------------------- | --------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Booked, Modified, Closed                                                                                   | Confirmed             | Starts a verification if the reservation does not already have one.                                                                                                                                                          |
| Not Completed, Attempt To Charge But Not Available, Non Blocked Request, Blocked Request, Quote Sent, BPen | Inquiry               | Skipped by default. These are quotes, requests, and bookings that are not complete, not a committed stay.                                                                                                                    |
| Cancelled, Deleted, No-Shows                                                                               | Canceled              | Withdraws the reservation's verification while it is still waiting on the applicant or on your account's funds. A verification that is already being checked, or that has a decision, is not withdrawn and keeps its result. |
| Any other status                                                                                           | None                  | Skipped. A status the integration does not recognize never starts a verification.                                                                                                                                            |

A reservation that starts a verification gets its verification link as soon as it qualifies. The verification itself starts when the reservation's verification opens, which with the default timing is at once. Streamline sends stay dates without a time or a time zone, so a timing measured from check-in uses the start of the check-in date in UTC.

<Aside type="note" title="Which reservations create a verification">
  Two routing rules are added for you when you connect. The first skips quotes and requests by
  matching **Record status: Inquiry**. The second skips owner stays and maintenance blocks by
  matching **Record type** against `ABL`, `MaintenanceBlock`, and `OWN`, the reservation types
  Streamline uses for them. You own both rules: you can edit or remove them, and you can add rules
  of your own (for example, to skip a particular distributor). If your company records owner stays
  under another reservation type, add that type's name to the second rule. Cancelled, Deleted, and
  No-Shows reservations are handled without a rule: a cancellation withdraws a matching verification
  that is still waiting on the applicant or on your account's funds, rather than starting a new one;
  one already being checked or decided keeps its result.
</Aside>

<Aside type="note" title="The integration is forward-only">
  The integration only reads a reservation that is created or changes after you connect; it does not
  use the date a reservation was originally created to choose which reservations to read. A
  reservation that has not changed since you connected is never read, no matter how old it is. A
  reservation whose departure date is more than a day in the past is not read either. But an older
  reservation that changes for the first time after you connect is read and treated like a new one:
  if it does not already have a verification, one starts, and you are billed for it. To keep a
  specific older reservation from starting a verification this way, add a routing rule that matches
  its **Confirmation code** (the Streamline confirmation number) before it next changes. A
  verification you start yourself for that reservation, through the API or a bulk CSV import, is not
  linked to it: the integration still starts its own when the reservation changes, and neither one
  gets the status flag or the notes.
</Aside>

Only the status flag and the two link notes are ever written back to Streamline. No applicant personal data is sent to Streamline.

### Reservation fields you can use in routing rules

Routing rules match on the fields the integration reads from each Streamline reservation. On a Streamline connection, the rule builder names a few of these fields the way Streamline does. The first column below is the name that you look for in the rule builder. The table lists the rows in alphabetical order, the same order as the rule builder. The other columns show where the value comes from on the reservation, and how **is one of** compares it:

| Rule field           | Taken from the Streamline reservation                                                                                                                           | How **is one of** compares it                       |
| -------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------- |
| Confirmation code    | The Streamline confirmation number.                                                                                                                             | Ignoring capitalization.                            |
| Distribution channel | The name of the reservation's distribution channel. A separate field from Distributor below.                                                                    | Ignoring capitalization.                            |
| Distributor          | The name of the reservation's distributor.                                                                                                                      | Ignoring capitalization.                            |
| Email                | The applicant's email, falling back to the second and third email addresses when the first is empty.                                                            | Ignoring capitalization.                            |
| End date             | The reservation's end date, in the form `2026-10-25T00:00:00`.                                                                                                  | Exactly, so enter the date followed by `T00:00:00`. |
| First name           | The applicant's first name.                                                                                                                                     | Ignoring capitalization.                            |
| Full name            | The first name and last name, joined by a space.                                                                                                                | Ignoring capitalization.                            |
| Last name            | The applicant's last name.                                                                                                                                      | Ignoring capitalization.                            |
| Lead time (days)     | The whole days between the reservation's creation date and its start date.                                                                                      | As a whole number of days, so +03 matches 3.        |
| Location ID          | The id of the location the reservation's unit belongs to.                                                                                                       | Exactly, including capitalization.                  |
| Phone                | The mobile phone, falling back to the phone, then the work phone.                                                                                               | Digits only, so any punctuation you use is fine.    |
| Record status        | The reservation's status, normalized to the values in the table above.                                                                                          | Exactly, from the fixed list above.                 |
| Record type          | The reservation's type name, such as `OWN`.                                                                                                                     | Ignoring capitalization.                            |
| Reference ID         | The record's reference: your Streamline company id and the confirmation number, joined by a colon, for example `1234:56789`. Reviewers see it as **Record ID**. | Exactly, including capitalization.                  |
| Start date           | The reservation's start date, in the form `2026-10-19T00:00:00`.                                                                                                | Exactly, so enter the date followed by `T00:00:00`. |
| Unit ID              | The id of the reservation's unit.                                                                                                                               | Exactly, including capitalization.                  |

**is not one of** and **is not one of, or empty** ignore invisible characters and treat different forms of the same character as equal, such as a full-width `Ａ` and `A`. On the fields marked Exactly, they also ignore capitalization and spaces at the start and end.

A few rows are worth a second look:

- **Use Confirmation code to match the Streamline confirmation number.** Reference ID holds the same number with your company id in front of it, so a rule on Reference ID matches only the whole value, for example `1234:56789`, never the confirmation number by itself.
- **Record status is ours, not Streamline's.** It is the reservation's Streamline status put through the table above, so a rule on it picks from Confirmed, Inquiry, Pending, Canceled, and Excluded, never from Booked, Quote Sent, or Cancelled. A Streamline reservation only ever carries Confirmed, Inquiry, or Canceled.
- **Record type is the reservation type's name as Streamline stores it.** That is how the owner-stay rule recognizes `OWN`. Check the type names your company uses for owner stays and maintenance blocks, and add any that the rule does not list.
- **Distribution channel and Distributor are two separate fields.** To skip everything from one booking source, you may need a rule on each.
- **Start date and End date are dates without a time.** A rule compares the whole value, so enter the date in the form shown, followed by `T00:00:00`.
- **Lead time (days) is worked out from two dates that Streamline records.** It counts the calendar days from the reservation's creation date to its start date. A reservation that Streamline records as created at 9:30 PM on the evening before its start date has a lead time of `1`, not `0`. `0` is the same day. A reservation created after its start date has a negative lead time. The integration uses the dates as Streamline writes them and does not move either one to another time zone. It counts the same way whether it reads the reservation in a batch of changed reservations or on its own, and it never uses the day the integration read the reservation. The rule builder also offers **is less than**, **is at most**, **is greater than**, and **is at least** for this field. The [Integrations overview](/guides/integrations#routing-rules) describes them.
- **A reservation with no lead time matches no condition on it.** A reservation has no lead time if Streamline sends no creation date, if the creation date is not in the form the integration reads, or if the reservation has no start date. Whatever the operator, no condition on Lead time (days) matches such a reservation. So a **Skip verification** rule on this field never skips it.

A field that is empty on the reservation is empty to the rule as well. A condition that uses **is one of** or **is not one of** never matches an empty field. A condition that uses **is not one of, or empty** matches it. If a rule has no effect, first make sure that its fields are not empty on the reservation.

A value that the integration cannot read, such as a list where Streamline usually sends a name, is also empty to the rule. So a condition that uses **is not one of, or empty** matches it. A **Skip verification** rule with that condition can then skip the reservation.

A rule can have more than one condition, and it matches a reservation only when all of them match. For example, a rule can have two conditions: Unit ID **is one of** `L-100`, and Distributor **is not one of** `Example Channel`. That rule matches each reservation at unit `L-100` whose Distributor is not empty and is not `Example Channel`, in any capitalization. A reservation at that unit whose Distributor is empty does not match it. The [Integrations overview](/guides/integrations#routing-rules) describes each operator.

## Status flag and notes on the reservation

The integration writes back using one reservation flag, which you create in Streamline before you connect, and two internal notes.

### Status flag

The integration sets the flag named `ID_VERIFICATION_STATUS` (or the name you enter in the connection's settings) on each reservation it screens, from the first time it reads the reservation, and keeps it set. The flag's comment carries the status, and the integration replaces the comment as the screening progresses. The comment says **Guest screening** rather than naming one kind of check, because a workflow may run an ID check, a background check, or neither: it reports how far the applicant's screening has progressed, whatever checks it contains.

| Flag comment                               | When it is written                                                                                       |
| ------------------------------------------ | -------------------------------------------------------------------------------------------------------- |
| Guest screening: Pending                   | The screening has started and has not yet reached review.                                                |
| Guest screening: In review                 | The screening is awaiting your team's review, or finished with no outcome recorded yet.                  |
| Guest screening: Approved                  | The screening was approved.                                                                              |
| Guest screening: Declined                  | The screening was declined.                                                                              |
| Guest screening: Not completed             | The screening expired, or was canceled without reaching an outcome.                                      |
| Guest screening: Not yet open              | Screening for the reservation has not opened yet.                                                        |
| Guest screening: Not started               | Screening for the reservation is open, and no screening is in progress for the guest.                    |
| Guest screening: Not completed by deadline | The screening deadline passed before the guest finished, or too little time was left to start screening. |

<Aside type="note" title="If your company used our earlier Streamline integration">
  This integration writes its own flag and not the flags the earlier integration used, so filters
  you built on those flags keep reading them. Create `ID_VERIFICATION_STATUS` as a new flag; do not
  rename one of the earlier flags.
</Aside>

### Applicant link and review link

The integration adds two internal notes to the reservation:

- **Screening link for the guest** carries the reservation's verification link. It is added as soon as the reservation qualifies, before any verification starts. Share this with the applicant if you send invites yourself.
- **Screening review link** carries an internal link your team uses to open the verification in the console. It is added when the verification starts. Not for the applicant.

Both notes are internal notes, which the applicant does not see. A note is not edited or recreated afterward, so a note you remove by hand stays removed. The reservation's verification link stays the same for the whole verification window. If it changes, because the reservation is restored in Streamline after a cancellation or is given a different guest name or email, the integration adds a new **Screening link for the guest** note, and the link in the earlier note stops working. Correcting the spelling of the guest's name or email also changes the link; a change of capitalization or spacing alone does not, and neither does moving the reservation to another client record with the same name and email. A canceled reservation's link stops working, and no new note is added. If the answer to a note write is lost on the way back, the integration writes the note again, so a reservation can occasionally carry more than one identical copy of a note. You can always find both links by opening the verification directly in your Applicants list, whether or not the note is still there.

## Connecting Streamline

You need the **Owner** or **Admin** role, an active organization, and at least one [workflow template](/guides/workflows/workflow-templates-create) to bind the connection to. Create a workflow first if you do not have one; the connect form links you to the workflow editor when none exist.

You connect using a Streamline **token pair** for this integration: a **token key** and a **token secret**. You also create the status flag in Streamline first, because the connection is refused while the flag is missing.

<Steps>

1. In the Streamline admin portal, open **Main Menu → Third-Party Integrations → Self-Serve Onboarding**, select the listing for this integration, and choose **Get Tokens**. Streamline shows an API key and a secret key. Copy both and keep them somewhere safe until you have connected.

2. In the Streamline admin portal, open **Tools → Configuration Settings → Manage Reservation Flags** and choose **Add Reservation Flag**. Enter the name `ID_VERIFICATION_STATUS` and a description, for example `Guest screening status`, and save the flag. Create a new flag; do not rename an existing one.

3. In the console, open **Integrations** and choose **Streamline**.

4. Enter the API key in **Token key** and the secret key in **Token secret**.

5. Check the **Status flag name**. It is filled in with `ID_VERIFICATION_STATUS`. If another tool already uses a flag with this name, create a flag with a different name in Streamline and enter that name here instead. You can change it later in the connection's edit form.

6. Choose the **default workflow** the integration runs for each reservation. This is required. Every verification the connection creates uses this workflow unless a routing rule skips it or selects another workflow. The list shows your active workflows, with your organization default marked.

7. (Optional) Change the **routing rules**. The connection starts with the two rules described above; you can keep them, edit them, or remove them, and add rules of your own. Each rule has one or more conditions, and each condition compares a field (such as Record status or Distributor) with one or more values. When all of its conditions match, the rule either skips the reservation or selects the workflow it runs.

8. (Optional) Turn on the **Send the verification invite** toggle to have the platform email each applicant their verification link. It is off for a new connection. Leave it off if you plan to send the link yourself from Streamline using the note described above.

9. (Optional) Set the **Verification timing**. By default, verification opens when a reservation reaches Checktiv and is due at the first verification's own deadline. To open it later or make it due at another time, see [Verification timing](/guides/integrations/verification-timing).

10. Select **Connect**.

</Steps>

When you select Connect, the platform first checks that the token pair can do each action the integration needs except renewing (see [About the token pair](#about-the-token-pair)), without writing anything to your reservations, and then looks for the status flag by its name. Once both checks pass, the connection appears in your Integrations list.

### About the token pair

<Aside type="caution" title="The integration renews the token pair automatically">
  A Streamline token pair has an end date, so the integration renews the pair on its own before that
  date. After the first renewal, the pair you entered no longer works. Any other integration that
  uses the same pair stops working too. Your company holds one token pair for this listing, so you
  cannot get a separate pair for another integration.
</Aside>

The token pair must be allowed every action the integration uses: reading reservations and your company's flags, setting a flag, adding a note, and renewing its own token. Streamline decides which actions a pair is allowed.

- At connect, a pair that is not allowed to read reservations, read flags, set a flag, or add a note is refused with: "The connected system does not allow some of the actions this integration needs. Have it allow them for these credentials, then connect again." Have Streamline allow those actions for the pair, then connect again.
- Renewing cannot be checked at connect without renewing the pair, so a pair that is not allowed to renew shows a connection issue when the integration first renews it. If a pair loses an action later, the connection shows the same issue: "The connected system does not allow some of the actions this integration needs. Have it allow them for these credentials, then save the connection's settings to check again." Have Streamline allow those actions for the pair, then open the integration, choose **Edit**, and save.

### One connection for each Streamline company

One Streamline company connects once. That covers test and live modes together: a connection in test mode holds the company until you disconnect it, so disconnect a test connection before you connect the same company in live mode.

A connection that shows **Reconnect needed** no longer holds the company. Anyone who has a token pair that Streamline accepts for the company can then connect it again, here or in another organization. Reconnect promptly to keep the company on your connection.

If the company is already held, Connect is refused with one of these messages:

- "This account is already connected in this organization, possibly in the other mode (test or live). Open that integration and reconnect, resume or disconnect it there. Disconnecting discards its stored credentials, so connecting again may need new ones: get them in the connected system's own settings where your account offers that, or from its support team otherwise." The company has a connection in your own organization, in this mode or the other one. Use that connection instead of adding a second one.
- "This account is connected to another organization. If you manage that organization, disconnect it there. Otherwise, renew this account's credentials in the connected system's own settings where your account offers that, or ask its support team to renew them, then connect here with the new ones. Disconnecting discards the stored credentials, so connecting again may need new ones from the connected system's settings or its support team." Renew the token pair in Streamline, or through Streamline support. When the other organization's connection can no longer use its pair, it shows **Reconnect needed** and no longer holds the company, so you can connect it here with the new pair. A paused connection keeps the company until it is resumed or disconnected in that organization.

## While Streamline needs reconnecting

If Streamline no longer accepts the stored token pair, for example because it was renewed or revoked outside the integration, the connection shows **Reconnect needed** and stops reaching Streamline: it stops checking for new and updated reservations, and any status flag or note that would be written back is held instead. Nothing already written to Streamline is undone.

To reconnect, you need a NEW token pair from Streamline. The integration renews the pair automatically, so after the first renewal the pair you first entered no longer works. Renew the pair in Streamline where your account offers that; otherwise, email Streamline support and ask them to renew it.

Once you reconnect with a working token pair, the integration picks up where it left off: it resumes checking Streamline from before the interruption, so reservations that changed while it needed reconnecting are still read. It also rebuilds the status flag and both notes for every verification that was waiting, as long as it had been waiting less than 14 days; reconnect promptly, since one waiting longer is not rebuilt automatically. For a reservation that has a screening window, the 14-day limit does not apply to the reservation's status flag and its **Screening link for the guest** note. They are rebuilt until 30 days after the latest of these dates: the day screening opens, the screening deadline, and the check-out date. For a canceled reservation, they are rebuilt until 30 days after the cancellation. You do not need to do anything else beyond reconnecting.

<Aside type="tip" title="Reconnecting">
  Open the integration and choose to reconnect, then enter the new **Token key** and **Token
  secret**; both are required. Your workflow choice, status flag name, routing rules, and invite
  setting are preserved through a reconnect. You cannot use reconnect to move the connection to a
  different Streamline company: a pair for another company is refused with "To connect a different
  account, add a new connection." If the integration is renewing the token pair at that moment, the
  reconnect is refused with "This integration's credentials are being renewed right now. Try again
  in a few minutes." Wait a few minutes, then reconnect again.
</Aside>

## If you see "Some updates from the connected system could not be read"

When an unusually large or fast-changing batch of reservations cannot be fully read after repeated attempts, the integration sets that period aside instead of getting stuck on it, and shows this notice on the connection:

> Some updates from the connected system could not be read. Check recent records and send verification links if needed, then dismiss this notice.

This can happen when thousands of reservations change at about the same time, for example in a bulk edit. For the period the notice covers, the integration may have missed more than a status update: a new reservation that should have started a verification, and a cancellation that should have withdrawn one (so you could be billed for a verification you no longer need). Reservations outside that period are unaffected, and the connection keeps working normally afterward.

If you see this notice, compare your recent reservations in Streamline against your Applicants list for the affected period and act on anything missing: start a verification for a reservation that should have one, or cancel one you no longer need. Neither a verification you start by hand nor one the integration starts carries the transaction amount, currency, or location; if your workflow's document prints them, use the API with the `metadata` object.

Once you have checked, select **Dismiss** on the notice to clear it. Entering a new token pair for the connection, with **Reconnect** or **Edit**, also clears it. It does not clear on its own.

## Troubleshooting

**The connection did not go through.**
Check the message the console shows:

- "These credentials were not accepted. Check the values you entered and try again." Check the token key and token secret against what Streamline showed you. If the integration has already renewed the pair, or the pair was renewed elsewhere, the pair you have no longer works: get a new pair from Streamline.
- "The connected system does not allow some of the actions this integration needs. Have it allow them for these credentials, then connect again." See [About the token pair](#about-the-token-pair).
- "Create a flag with the name entered in this form in your system, or enter the name of the flag you created, then try again." No flag in your Streamline company has the name in **Status flag name**. Create the flag (step 2 of [Connecting Streamline](#connecting-streamline)), or correct the name in the form.
- "More than one flag in your system has the name entered in this form. Rename one, or enter a different name, then try again." Names are compared ignoring capitalization and spaces at either end, so two flags whose names differ only that way count as the same name. Rename one in Streamline, or enter the name of a different flag.
- "This account is already connected in this organization, possibly in the other mode (test or live)." or "This account is connected to another organization." See [One connection for each Streamline company](#one-connection-for-each-streamline-company).
- "The connected system is not responding. Try again in a few minutes." Streamline was temporarily unavailable. Wait a moment and try connecting again.
- "This integration's credentials are being renewed right now. Try again in a few minutes." This shows when you reconnect, or enter a new token pair with **Edit**, while the integration is renewing the pair. Wait a few minutes, then reconnect or save again.

**The connection shows "Reconnect needed."**
Streamline no longer accepts the stored token pair, usually because it was renewed or revoked outside the integration. Get a NEW token pair from Streamline: renew it in Streamline where your account offers that, otherwise email Streamline support. The pair you first entered no longer works after the integration's first renewal. Then open the integration, choose to reconnect, and enter the new token key and token secret. See [While Streamline needs reconnecting](#while-streamline-needs-reconnecting) above for what happens to reservations and write-backs in the meantime.

**The connection shows "Not responding. We will keep retrying automatically."**
Streamline has been unreachable or timing out for a while. This clears on its own once Streamline responds normally again; you do not need to do anything.

**The connection is paused and shows "The saved credentials are no longer accepted. Use Edit to enter working credentials to resume."**
Get a NEW token pair from Streamline, as for Reconnect needed: renew it in Streamline where your account offers that, otherwise email Streamline support. Then edit the connection and enter the new token key and token secret. Saving working credentials returns the connection to active on its own; there is no separate step after that. Trying to resume the connection before that is done shows: "Enter working credentials for this integration to resume."

**The status flag is not updating.**
The connection shows: "Status updates are on hold: the flag named in this connection's settings is missing in the connected system, or more than one flag has that name. Create or rename the flag there, or change the name with Edit, then save the connection's settings to check again." The flag named in the connection's settings (`ID_VERIFICATION_STATUS` unless you changed it) was deleted or renamed in Streamline, or a second flag now has the same name. Do one of these:

- Create the flag again in Streamline.
- Rename the duplicate flag in Streamline.
- Open the integration, choose **Edit**, and enter the name of the right flag.

Then save the connection's settings. Saving checks the name again and brings the status flag up to date on the reservations whose status changed in the meantime. Until then, polling, new verifications, and the notes go on as usual.

**The connection shows "The connected system does not allow some of the actions this integration needs."**
The token pair is no longer allowed one of the actions the integration uses. Have Streamline allow those actions for the pair, then open the integration, choose **Edit**, and save. See [About the token pair](#about-the-token-pair).

**A reservation did not create a verification.**
Check, in order:

- **The verification timing.** A reservation whose verification has not opened yet already has its link note, and its flag comment is **Guest screening: Not yet open**. Its verification starts when verification opens. See [Verification timing](/guides/integrations/verification-timing).
- **The reservation status.** Only Booked, Modified, and Closed reservations start a verification, and only when the reservation does not already have one. A quote or a request is skipped, and a Cancelled, Deleted, or No-Shows reservation never starts one. See the [status table](#what-each-reservation-status-does) above.
- **Routing rules.** A reservation that matches a Skip rule is intentionally not verified, and one that matches a Select workflow rule runs that rule's workflow instead of the default. Review the connection's rules, including the two rules added at connect (Record status: Inquiry, and Record type: `ABL`, `MaintenanceBlock`, `OWN`), against the reservation's fields.
- **The check schedule.** The integration checks Streamline roughly every 5 minutes, so a very recently changed reservation may not have been picked up yet.
- **Whether the reservation has changed since you connected.** The integration only reads a reservation that changes after you connect, and never one whose departure date is more than a day in the past. See [The integration is forward-only](#what-each-reservation-status-does) above.
- **The workflow.** The connection must be bound to an active workflow. A workflow an integration uses cannot be deactivated or deleted from the console or the API, but a connection set up before that protection can still point at an inactive default workflow. The connection's form flags it; edit the connection and choose an active one.

**An applicant did not receive their invite.**
Confirm the **Send the verification invite** toggle is on for the connection. A new connection starts with it off, and while it is off the platform does not email the applicant; you are expected to send the link yourself using the note the integration wrote onto the reservation. Turning it on invites each applicant whose verification opens after the change. To invite an applicant whose verification already started, open it in your **Applicants** list and select **Send invite** (see [Resend or revoke](/guides/verification/send-an-invite#resend-or-revoke)). If their verification has not started yet, share the link in the note the integration wrote onto the reservation. Also confirm the reservation carried an email address for the applicant, since there is no address to send to otherwise. If that email address reached the [per-recipient invite limit](/developers/rate-limits#per-recipient-invite-limit) of three invite emails in an hour, the verification starts but Checktiv sends no invite. Open that verification in your **Applicants** list and select **Send invite**.

**A note is missing from the reservation.**
The integration adds the screening link note when the reservation qualifies and the review link note when the verification starts, and does not recreate a note removed afterward. You can still find both links by opening the verification directly in your Applicants list.

**You want to stop the integration.**
Pausing stops the integration from checking Streamline for new and updated reservations, but it does not stop a write-back already under way: a verification that was already in progress keeps updating its status flag as it moves through review, since that happens independently of the check schedule. Reservations that change while paused are not read once you resume, unless they change again afterward; resuming does not catch up the way reconnecting does. A paused connection's token pair is not renewed, so a pause longer than the pair's remaining life may end in **Reconnect needed**.

While a connection is paused, an applicant who opens their link is asked to try again later.

Disconnecting removes the connection entirely and stops all future write-backs. Verifications that already started continue either way, but disconnecting also makes the verification links on your reservations stop working; after you connect again, a reservation gets a new link the next time it changes in Streamline. Disconnecting also discards the stored token pair. Because the integration renews the pair automatically, the pair you first entered stops working after the first renewal, so to connect again you usually need a new token pair from Streamline: renew it in Streamline where your account offers that, otherwise email Streamline support.

## Related

- [Integrations overview](/guides/integrations)
- [Create a verification workflow template](/guides/workflows/workflow-templates-create)
- [Glossary](/glossary)