Yadulink / Documentation / API

Use Yadulink API keys without exposing your LinkedIn account.

The public Yadulink API connects signals, lists, and actions to external systems through readable, auditable permissions.

View API documentation All guides

API

Scopes and least privilege

Each automation should receive only the rights it needs. A reporting recipe does not need the same scopes as a sales activation workflow.

API

Recommended architecture

Avoid exposing keys in the browser. Place API calls in a backend, n8n, Make, Zapier, or server job, then log sensitive operations.

Verified facts

What this documentation should make explicit.

Purpose

The public Yadulink API connects signals, lists, and actions to external systems through readable, auditable permissions.

Workflow proof

Each automation should receive only the rights it needs. A reporting recipe does not need the same scopes as a sales activation workflow.

Assistant prompt

Review this Yadulink API authentication approach and list the minimum scopes for a secure LinkedIn prospecting workflow.

Verification method

How to turn the guide into an operational test.

  1. 01 Setup Create an API key from the integrations area.
  2. 02 Setup Choose the most restrictive scopes for the workflow.
  3. 03 Setup Store the key server-side or in your automation tool's secret manager.

Ask your preferred AI.

ChatGPT Claude Perplexity Codex

Docs linking

Guides to read next.

Webhooks

Yadulink webhooks: sync replies, reads, and LinkedIn signals

Turn LinkedIn events into CRM actions and sales alerts.

n8n

Automate Yadulink with n8n: LinkedIn and CRM recipes

Build n8n workflows around Yadulink LinkedIn signals.

MCP

Set up Yadulink MCP with Claude, ChatGPT, and AI assistants

Connect Yadulink to Claude, ChatGPT, or an MCP-compatible assistant.