Draftboard API: Add Relationship Intelligence to Your GTM Stack

Updated September 28, 2026: the API details below now match the current Integration API reference.

Why an API?

Your sales team uses dozens of tools - CRM, sequencing, enrichment, analytics. Relationship intelligence shouldn't live in a silo. The Draftboard Integration API lets you bring relationship data directly into the tools your team already uses.

What the API Provides

Warm paths and relationship scores:

List your targets with their relationship score and degree (1st or 2nd)
Get every path to a target: the connector who can introduce you, a 0-100 relationship score, and the reasons behind it
See which teammates know each connector, and how well

Relationship context:

The reasons behind each score, as plain sentences
Structured facts where Draftboard holds them: shared employers and schools with overlap dates, and mutual-connection counts
How the connector knows the target: current colleague, former colleague, or university classmate

Account-level view:

The companies where you have saved targets, strongest first, with target and path counts and the best score at each
The companies where you have saved targets but no path yet

Adding targets and tracking intros:

Import targets by LinkedIn profile URL, or start a search for people with given titles at given companies
Mark an intro as requested, completed, or declined, so your tools and Draftboard agree on where each one stands

Common Use Cases

1. CRM Enrichment

Add relationship data directly to Salesforce, HubSpot, or your CRM of choice.

What it enables:

Reps see warm paths without leaving CRM
Relationship score as a lead scoring factor
Automatic routing based on relationship strength

2. Outbound Sequence Personalization

Feed relationship context into Outreach, Salesloft, or Apollo.

What it enables:

Personalization with the name of the connector and the shared history behind the path
Segment sequences by relationship score
Trigger different cadences based on path strength

3. Account Prioritization

Use relationship coverage as an ICP scoring factor.

What it enables:

Prioritize accounts with strong warm paths
Surface "hidden gem" accounts with unexpected connections
Spot the target accounts where you have no path yet

4. Custom Dashboards

Build relationship intelligence into your internal tools.

What it enables:

Network coverage reporting
Connector leaderboards
Path analysis by tag or segment

The Endpoints You'll Use Most

Every request goes to https://intros.draftboard.com with the header Authorization: Bearer followed by your token.

GET /api/v1/integration/accounts - the companies where you have saved targets, strongest first, each with its target count, path count, 1st- and 2nd-degree counts, and best score. Filter with query (a company name, or a saved person's name or job title) and connectionDegree (1st, 2nd, or none).
GET /api/v1/integration/targets - your targets that already have a warm path, with score, degree, and tags. Filter by accountId, title, tags, status, or updatedSince.
GET /api/v1/integration/targets/resolve - find one of your targets by LinkedIn profile URL, including one whose paths haven't been found yet.
GET /api/v1/integration/targets/{target_id}/connections - every path to a target: the connector, a 0-100 score, the reasons, and the teammates (owners) who know the connector.
POST /api/v1/integration/targets/import - add targets by LinkedIn profile URL.
POST /api/v1/integration/search/accounts - start a search for people with given titles at given companies (a website domain or LinkedIn company URL each). People turn up in your Backlog (the API's /pool) over time, and become targets once you confirm them with POST /api/v1/integration/pool/confirm; there is no "search complete" signal.
POST /api/v1/integration/intros/{intro_id}/requested, /completed, and /declined - update an intro's status.

The full list, including tags, supporters, connectors, and the team Shortlist, is in the Integration API reference.

Example: CRM Integration

Goal: Show the warmest paths into an account on its Salesforce record.

Approach:

Find the company: GET /api/v1/integration/accounts?query=Acme
List its targets: GET /api/v1/integration/targets?accountId=(the account's id), adding &title=VP%20of%20Sales to narrow by role
Get the paths to a target: GET /api/v1/integration/targets/{target_id}/connections
Store the strongest path in custom fields and add them to the page layout

Sample response from step 3, trimmed from the reference:

{
  "status": 200,
  "errors": [],
  "connections": [
    {
      "id": "daf886d4-d2ca-4ca2-8cd7-5546c50ada5f",
      "firstName": "David",
      "lastName": "Chen",
      "position": {
        "title": "Director of Engineering",
        "companyName": "Draftboard"
      },
      "score": 48,
      "scoreDetails": [
        "They overlapped for a long time (42 months) @ TechCorp, most recently in 2016"
      ],
      "relationships": ["former_colleague"],
      "relationshipDetails": [
        {
          "employment": {
            "company": "TechCorp",
            "overlapStartDate": "2012-09-01",
            "overlapEndDate": "2016-03-01",
            "loose": false
          },
          "score": 0.42
        },
        {
          "mutualConnections": { "count": 17 },
          "score": 0.08
        }
      ],
      "owners": [
        {
          "id": "0dda7490-eea3-4c1c-8cec-a4824222f116",
          "firstName": "John",
          "lastName": "Smith",
          "score": 85
        }
      ]
    }
  ],
  "count": 68,
  "nextPage": 2
}

Each connection's id is also the intro id you pass to the intro-status endpoints. The scoreDetails, relationships, and relationshipDetails fields are left out when Draftboard holds no signal for that pair, so read them defensively.

What reps see:

A panel on the Salesforce record showing:

"David Chen (48): overlapped 42 months at TechCorp, most recently in 2016"
"John Smith on your team knows David (85)"

Example: Outbound Personalization

Goal: Personalize outreach with real relationship context.

Approach:

Before sequence enrollment, find the prospect with GET /api/v1/integration/targets/resolve?linkedinUrl=(their profile URL)
Get their paths with GET /api/v1/integration/targets/{target_id}/connections
Write the strongest connector's name and first score reason into custom fields in your sequencing tool
Use the fields in email templates

Template:

Hi {{first_name}},

{{#if connector_name}}
I noticed we're both connected to {{connector_name}} -
{{connection_context}}.
{{/if}}

[Rest of email...]

Output:

"I noticed we're both connected to David Chen - you two overlapped at TechCorp."

Getting Started

Step 1: Create an API token

In the Draftboard app, open Settings → API Keys and create a token. Send it on every request as Authorization: Bearer followed by the token. Keys aren't scoped - a valid key reaches every endpoint - so store it like a password.

Step 2: Read the reference

Every endpoint, field, and error code is in the Integration API reference.

Step 3: Start with a simple integration

Begin with a single use case (e.g., CRM enrichment) before expanding.

Step 4: Monitor and iterate

Track how relationship data impacts your metrics.

Want these answers inside ChatGPT, Claude, or Codex rather than your own code? Connect Draftboard's hosted MCP server instead - it needs no token.

Integration Patterns

Real-time lookup:

Query the API at the moment data is needed (e.g., when a rep opens a record).

Pros: Always fresh data

Cons: Latency, and every lookup counts against your rate limit

Batch sync:

Periodically sync relationship data to your systems. GET /api/v1/integration/targets and GET /api/v1/integration/targets/{target_id}/connections both accept updatedSince, so each sync can fetch only what changed since the last one.

Pros: No latency for end users, efficient

Cons: Data can be stale between syncs

No webhooks:

The Integration API doesn't send webhooks. To pick up changes, poll with updatedSince.

Security & Compliance

Authentication:

A bearer token you create in the app under Settings → API Keys. A missing, unknown, or revoked token gets a 403; the API never returns 401.

Data handling:

The API only reaches your own organization's data; a resource that belongs to another customer is refused
Draftboard is SOC 2 Type II compliant and ISO 27001 certified, and your data is never sold

Rate limits:

Reads and writes have separate per-minute limits, and a write counts against both. Every response carries the headers X-RateLimit-Limit-{read|write}, X-RateLimit-Remaining-{read|write}, and X-RateLimit-Reset-{read|write}, one set per bucket; over a limit you get a 429 with the code rate_limited. The current limits are in the reference.

Credits:

Writes need a funded credit balance. When it runs out, writes return 402 with the code INSUFFICIENT_CREDITS; reads keep working.

What You Can Build

Sales teams:

Relationship data in Salesforce page layouts
Warm path alerts when high-value accounts are created
Prioritization scoring incorporating relationship strength

RevOps teams:

Network coverage dashboards
Attribution tracking for relationship-sourced pipeline, using intro statuses
Territory planning based on relationship density

Conclusion

Your GTM stack becomes more powerful when it understands relationships. The Draftboard Integration API lets you bring relationship intelligence wherever your team works - CRM, sequences, analytics, or custom tools.

Draftboard API: Add Relationship Intelligence to Your GTM Stack

Why an API?

What the API Provides

Common Use Cases

The Endpoints You'll Use Most

Example: CRM Integration

Example: Outbound Personalization

Getting Started

Integration Patterns

Security & Compliance

What You Can Build

Conclusion

Related Reading

Ready to find warm intros?