# Connecting Reo.dev

> Source: https://docs.trailspark.ai/docs/connecting-reo-dev

## Overview

Reo.dev connects as a **feed**: once you connect it and choose which segments to sync, TrailSpark checks those segments about once a day and matches what it finds against accounts you already track — bringing in developer buying-intent signals and company details along the way. Unlike Clay, there's no callback to set up on Reo.dev's side; the sync runs entirely from the TrailSpark side.

**The segments you select are the only scope control.** Reo.dev reads don't spend credits, so the eligibility rules and monthly/daily budget caps you may have seen for other enrichment providers don't apply to Reo.dev — TrailSpark's Reo.dev pages don't show them. What syncs is exactly, and only, the accounts in the segments you check off — and only for accounts you already track in TrailSpark. Nothing is ever created from a Reo.dev sync.

## Before you start (in Reo.dev)

Sign in to Reo.dev and go to **Configurations** > **API Keys** to generate an API key. You'll need an admin role in your Reo.dev account to create one.

## Step 1: Connect your API key

Go to **Settings** > **Integrations**, find **Reo.dev** in the **Data enrichment** section, and click **Configure**.

- **Connection name** — a label for this connection (e.g., "Reo.dev production")
- **API key** — paste the key you generated in Reo.dev. It's stored securely and never shown again.

Click **Connect**.

## Step 2: Choose your segments under "What syncs"

Once connected, open the **Enrichment rules** tab. For Reo.dev, this tab doesn't show the account rules or budget caps you may have seen for other providers — it shows a **What syncs** section instead: **"Choose which Reo.dev segments to sync. Accounts you don't already track are ignored."**

Check the box next to each segment configured in your Reo.dev account that you want TrailSpark to pull from — for example, a segment tracking developer activity or hiring signals. Click **Save**, then confirm. The confirmation step tells you plainly what you're about to turn on: **"Reo.dev syncs the accounts in your selected segments: [segment names]."** plus **"Only accounts you already track in Trailspark are updated — nothing new is ever created."**

If nothing is checked, TrailSpark shows a warning right in the **What syncs** section — and again in the confirmation step — instead of a rule count or credit estimate: **"No segments selected — nothing will sync until you choose at least one."** You can still save with nothing selected, but nothing will sync until you come back and check at least one segment.

## Step 3: Watch the sync status

Back on the **Connection** tab, a **Sync status** section shows where the daily sync stands:

- If no segment is selected: the same warning as above, **"No segments selected — nothing will sync until you choose at least one,"** appears immediately — you don't need to open the Enrichment rules tab to notice it.
- Before the first sync (with at least one segment selected): **"Waiting for the first sync."**
- After a sync runs: **"Last synced [time ago] — N accounts checked, M matched."**

"Checked" is how many accounts in your selected segments Reo.dev reviewed; "matched" is how many of those it was able to connect to an account you already track in TrailSpark. Unmatched accounts are dropped, not saved — Reo.dev never adds a new account or lead to your workspace.

## After you're connected

The connection page shows **"Reo.dev is connected."** Your API key is saved securely and never shown again — to replace it, disconnect and reconnect.

- **Test connection** verifies TrailSpark can reach Reo.dev with your key.
- **Disconnect** stops the daily sync. Reconnect and re-select your segments to resume it.

> [!NOTE]
> Reo.dev's Enrichment rules tab intentionally doesn't match [Enrichment Rules & Budget Caps](/docs/enrichment-rules-and-budget-caps) — that page describes the account-rule and budget-cap controls for a metered, on-demand provider like Clay. Reo.dev's reads are credit-free, so those controls don't exist for it; your segment selection is the whole story.

## Next Steps

- [Third-Party Intent & Field Provenance](/docs/how-enriched-data-shows-up) — how Reo.dev's intent is labeled and never drives a score alone
- [Connecting Clay](/docs/connecting-clay) — add a second enrichment source, with its own rules and budget caps