← 返回
安全合规 Key 中文

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...
通过公共API运行Dievio潜在客户搜索和LinkedIn查询工作流,包含正确的身份验证、筛选、分页及额度感知处理。
hundevmode
安全合规 clawhub v1.0.3 1 版本 100000 Key: 需要
★ 0
Stars
📥 785
下载
💾 5
安装
1
版本
#latest

概述

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

版本历史

共 1 个版本

  • v1.0.3 当前
    2026-03-29 23:12 安全 安全

安全检测

腾讯云安全 (Keen)

安全,无风险
查看报告

腾讯云安全 (Sanbu)

安全,无风险
查看报告

🔗 相关推荐

communication-collaboration

Twitter/X scraper with Apify actors

hundevmode
用于通过Apify actors收集Twitter/X受众(关注者/被关注者/两者),可选邮件增强。
★ 1 📥 784
security-compliance

Skill Vetter

spclaudehome
AI智能体技能安全预审工具。安装ClawdHub、GitHub等来源技能前,检查风险信号、权限范围及可疑模式。
★ 1,211 📥 266,213
security-compliance

MoltGuard - Security & Antivirus & Guardrails

thomaslwang
MoltGuard — OpenClaw 安全守卫,由 OpenGuardrails 提供。安装 MoltGuard,保护您和您的用户免受提示注入、数据泄露和恶意攻击。
★ 116 📥 30,701