ClawHub

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.

Audits

Pass
ClawScanPass

Agentic behavior and permission review.

Static analysisPass

Pattern checks against bundled files.

VirusTotalPass

Multi-engine malware detections and file reputation.

Install

openclaw skills install dievio-lead-search-api

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