How do I install the Dievio Lead Search API skill?

Run npx skillmds@latest add modbender/dievio-lead-search-api in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Dievio Lead Search API safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: executes scripts, makes network calls, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Dievio Lead Search API?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Dievio Lead Search API free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Dievio Lead Search API?

modbender (@modbender) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Dievio Lead Search API by modbender

Name: Dievio Lead Search API
Rating: 4.5 (4 reviews)
Author: modbender

Dievio Lead Search API

Run Dievio lead search and LinkedIn lookup workflows through the public API with correct authentication, filters, pagination, and credit-aware handling. Use this skill when users need to find B2B leads, enrich LinkedIn URLs with emails/phones, apply Dievio filter fields, or iterate across paginated API results safely.

modbender Updated Sep 9, 2026 12 repo stars

File contents

Dievio Lead Search Api

Overview

Use this skill for end-to-end Dievio API execution: authenticate requests, submit lead searches, enrich LinkedIn profiles, and paginate results. Prefer the bundled script for deterministic request formatting and response handling.

Core Endpoints

Public lead search: POST https://dievio.com/api/public/search
LinkedIn lookup: POST https://dievio.com/api/linkedin/lookup

Authentication headers (use one):

Authorization: Bearer YOUR_API_KEY
X-API-Key: YOUR_API_KEY

Workflow

Validate credentials:

Require DIEVIO_API_KEY for API-key flows.
Never print raw secrets.

Build request body:

Search endpoint uses pagination keys (_page, _per_page, max_results) plus filters.
LinkedIn lookup requires linkedinUrls and optional output flags.

Execute request and parse response:

Validate success, count, has_more, next_page, data arrays.
Respect credit behavior: low credits can return fewer rows than requested.

Handle errors:

401: missing/invalid credentials
402: insufficient credits
502: upstream lead service issue
500: server error

Commands

Show help:

python3 scripts/dievio_api.py --help

Search with JSON body:

export DIEVIO_API_KEY="your_api_key"
python3 scripts/dievio_api.py search \
  --body-file ./search_body.json \
  --auto-paginate

By default the CLI prints a safe summary. Use --raw-output only when you explicitly need full rows (which may contain emails/phones).

LinkedIn lookup from URLs:

python3 scripts/dievio_api.py linkedin-lookup \
  --linkedin-url "https://www.linkedin.com/in/example-1" \
  --linkedin-url "https://www.linkedin.com/in/example-2" \
  --include-work-emails \
  --include-personal-emails \
  --only-with-emails

Decision Rules

Use search when query is filter-based lead discovery.
Use linkedin-lookup when input is explicit LinkedIn profile URLs.
For large pulls, enable pagination and stop on has_more=false.
Keep outputs structured and include paging fields for traceability.
If user asks for exact filter values, read references/filters-cheatsheet.md.

References

API contracts: references/api-reference.md
Filter fields and allowed values: references/filters-cheatsheet.md
Pagination behavior: references/pagination.md
Error handling guidance: references/errors.md

---name: dievio-lead-search-apidescription: Run Dievio lead search and LinkedIn lookup workflows through the public API with correct authentication, filters, pagination, and credit-aware handling. Use this skill when users need to find B2B leads, enrich LinkedIn URLs with emails/phones, apply Dievio filter fields, or iterate across paginated API results safely.--- # Dievio Lead Search Api ## Overview Use this skill for end-to-end Dievio API execution: authenticate requests, submit lead searches, enrich LinkedIn profiles, and paginate results. Prefer the bundled script for deterministic request formatting and response handling. ## Core Endpoints - Public lead search: `POST https://dievio.com/api/public/search` - LinkedIn lookup: `POST https://dievio.com/api/linkedin/lookup` Authentication headers (use one): - `Authorization: Bearer YOUR_API_KEY` - `X-API-Key: YOUR_API_KEY` ## Workflow 1. Validate credentials: - Require `DIEVIO_API_KEY` for API-key flows. - Never print raw secrets. 2. Build request body: - Search endpoint uses pagination keys (`_page`, `_per_page`, `max_results`) plus filters. - LinkedIn lookup requires `linkedinUrls` and optional output flags. 3. Execute request and parse response: - Validate `success`, `count`, `has_more`, `next_page`, data arrays. - Respect credit behavior: low credits can return fewer rows than requested. 4. Handle errors: - `401`: missing/invalid credentials - `402`: insufficient credits - `502`: upstream lead service issue - `500`: server error ## Commands Show help: ```bash python3 scripts/dievio_api.py --help ``` Search with JSON body: ```bash export DIEVIO_API_KEY="your_api_key" python3 scripts/dievio_api.py search \ --body-file ./search_body.json \ --auto-paginate ``` By default the CLI prints a safe summary. Use `--raw-output` only when you explicitly need full rows (which may contain emails/phones). LinkedIn lookup from URLs: ```bash python3 scripts/dievio_api.py linkedin-lookup \ --linkedin-url "https://www.linkedin.com/in/example-1" \ --linkedin-url "https://www.linkedin.com/in/example-2" \ --include-work-emails \ --include-personal-emails \ --only-with-emails ``` ## Decision Rules - Use `search` when query is filter-based lead discovery. - Use `linkedin-lookup` when input is explicit LinkedIn profile URLs. - For large pulls, enable pagination and stop on `has_more=false`. - Keep outputs structured and include paging fields for traceability. - If user asks for exact filter values, read [references/filters-cheatsheet.md](references/filters-cheatsheet.md). ## References - API contracts: [references/api-reference.md](references/api-reference.md) - Filter fields and allowed values: [references/filters-cheatsheet.md](references/filters-cheatsheet.md) - Pagination behavior: [references/pagination.md](references/pagination.md) - Error handling guidance: [references/errors.md](references/errors.md)

Frequently asked questions