Load Linkedin-lead-forms data to DuckDB

LinkedIn Lead Forms API allows developers to retrieve and sync lead generation form submissions and manage lead form configuration. Everything needed to build a working Linkedin-lead-forms → DuckDB pipeline is on this page: the API's base URL, authentication, endpoints, pagination and incremental field — plus a prompt that hands the whole job to your coding agent.

---

Build your Linkedin-lead-forms to DuckDB pipeline

Paste this prompt into Claude, Codex, or Cursor. The agent does the rest.

PromptCopy prompt
Run uvx dlthub-init@latest to build a pipeline from Linkedin-lead-forms to DuckDB and run it on dltHub

That scaffolds a dltHub workspace and installs the dltHub AI harness — the project rules, the secrets-management skill, and the dlt MCP server your agent needs to work safely. From there it reads the Linkedin-lead-forms API, proposes the endpoints to load, then writes, runs and validates the pipeline while you review rather than type. Credentials are inspected through MCP tools, so your agent never reads secrets.toml itself. How the LLM-native workflow works →

Prefer to write it yourself? Every fact the agent uses is below.

---

Linkedin-lead-forms API at a glance

These values come from the Linkedin-lead-forms API reference — the authoritative source if anything here looks out of date.

---

How do I authenticate with the Linkedin-lead-forms API?

LinkedIn APIs use OAuth 2.0. Authenticated requests must include an 'Authorization' header with a 'Bearer {access_token}' value, a 'LinkedIn-Version' header specifying the API version (e.g., '202603'), and 'X-RestLi-Protocol-Version: 2.0.0'.

1. Get your credentials

1. Navigate to the LinkedIn Developer Portal and create a new application, or select an existing one. 2. Under the 'Products' tab, request access to the 'Ads Lead Sync' API; this requires formal approval from LinkedIn. 3. Navigate to the 'Auth' tab to retrieve your Client ID and Client Secret. 4. To generate an access token for development/testing, you can use the LinkedIn Marketing Solutions Workspace on Postman or the Token Generator tool in the Developer Portal. For production applications, implement the standard 3-legged OAuth 2.0 Authorization Code Flow: direct users to the LinkedIn authorization URL, handle the callback with the authorization code, and POST the code, client_id, client_secret, and redirect_uri to https://www.linkedin.com/oauth/v2/accessToken to obtain your production access token.

2. Add them to .dlt/secrets.toml

Copy
[sources.linkedin_lead_forms_source]
access_token = "REPLACE_ME"

dlt reads this file automatically at runtime. With the harness, the setup-secrets skill prompts you for the values and never handles the raw credential in chat. For production, see setting up credentials with dlt.

---

What Linkedin-lead-forms data can I load into DuckDB?

These are the Linkedin-lead-forms endpoints dlt can load into DuckDB:

---

How do I load only new Linkedin-lead-forms records?

The Linkedin-lead-forms API reference does not document a timestamp or sequence field for these endpoints, so there is nothing to advertise here as verified. Pick a field from the endpoints table above that increases with every write, then set it as the cursor_path.

Copy
{"name": "lead_forms", "endpoint": {
    "path": "leadForms",
    # Replace with a field that increases on every write.
    "incremental": {"cursor_path": "REPLACE_ME", "initial_value": "2024-01-01T00:00:00Z"},
}}

On the first run dlt loads everything from initial_value; on every run after that it requests only what changed and appends with write_disposition="merge" if you set a primary key. See incremental loading.

---

What does the generated Linkedin-lead-forms pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading leadForms and leadNotifications from the Linkedin-lead-forms API into DuckDB:

Copy
import dlt
from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources

@dlt.source
def linkedin_lead_forms_source(access_token=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://api.linkedin.com/rest/",
            "auth": {"type": "bearer", "token": access_token},
        },
        "resources": [
            {"name": "lead_forms", "endpoint": {"path": "leadForms", "data_selector": "elements"}},
            {"name": "lead_notifications", "endpoint": {"path": "leadNotifications", "data_selector": "elements"}}
        ],
    }
    yield from rest_api_resources(config)


def load_linkedin_lead_forms_to_duckdb() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="linkedin_lead_forms_pipeline",
        destination="duckdb",
        dataset_name="linkedin_lead_forms_data",
    )
    load_info = pipeline.run(linkedin_lead_forms_source())
    print(load_info)


if __name__ == "__main__":
    load_linkedin_lead_forms_to_duckdb()

Run it with python linkedin_lead_forms_pipeline.py. The agent iterates on this until it loads cleanly — you review and approve, rather than write it from scratch.

---

How do I query Linkedin-lead-forms data in DuckDB?

dlt creates one table per resource. Query the loaded data with Python or SQL — or ask your agent to, through the MCP server's execute_sql_query tool.

Python (pandas DataFrame):

Copy
import dlt

data = dlt.pipeline("linkedin_lead_forms_pipeline").dataset()
df = data.lead_forms.df()
print(df.head())

SQL:

Copy
SELECT * FROM linkedin_lead_forms_data.lead_forms LIMIT 10;

See querying your data with dataset and exploring it in marimo notebooks.

---

How do I deploy the Linkedin-lead-forms to DuckDB pipeline in production?

The pipeline runs locally, which is ideal for prototyping and one-off analysis. When you need it on a schedule, monitored on every load, and shared with your team, deploy the same dlt code on the dltHub platform — no infrastructure to maintain. The prompt above already ends with "run it on dltHub", so your agent can take it there directly.

• Deploy & schedule — run the pipeline as a managed job with automatic retries.
• Monitor — observable job queues, alerting, and load metrics for every run.
• Transform — promote raw Linkedin-lead-forms loads into governed, documented models.
• Visualize & share — explore data in notebooks and publish live dashboards instead of static screenshots.

Book a demo →

---

What other destinations can I load Linkedin-lead-forms data to?

dlt loads into any of these — only the destination argument changes:

Set dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. On the dltHub platform the same pipeline runs against a managed Iceberg lakehouse. See the full destinations list.

---

Next steps

• Ready for production? Book a demo of the dltHub platform →
• dlt LLM-native workflow docs
• REST API source reference
• Join the dlt community on Slack