Coding

Dievio Lead Search API

Try it

Run Dievio lead search and LinkedIn lookup workflows through the public API with correct authentication, filters, pagination, and credit-aware handling. Use...

What it does

Run Dievio lead search and LinkedIn lookup workflows through the public API with correct authentication, filters, pagination, and credit-aware handling. Use...

The skill document

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.
  1. Build request body:
  • Search endpoint uses pagination keys (_page, _per_page, max_results) plus filters.
  • LinkedIn lookup requires linkedinUrls and optional output flags.
  1. 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.
  1. 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

Related skills

Call LinkedIn's REST API with OAuth handled for you, covering posts, profiles, ad accounts, and the Ad Library.

411 installs45 stars

Extract structured real-estate lead records from parsed message objects. Use when users ask to find leads in WhatsApp exports, extract name-phone-budget, or...

49 installs

AI resume and cover letter generation powered by CellCog. ATS-optimized resumes, CVs, cover letters, LinkedIn profiles, career documents — PDF or DOCX. Research-first approach that analyzes target roles before writing.

49 installs1 stars

Schedule, draft, or publish social posts across 9 platforms via the AdaptlyPost API, with explicit confirmation before every post.

97 installs3 stars

Search, read, and update Pipedrive deals, contacts, organizations, activities, pipelines, and sales workflows through a local MCP wrapper. Use when the user...

25 installs

Access the Apollo.io API through a managed OAuth proxy to search, enrich, and manage sales data.

226 installs5 stars