Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.prontohq.com/llms.txt

Use this file to discover all available pages before exploring further.

​
Week of May 10, 2026

​
Updates

  • Filter leads by connections of a profile. POST /leads/advanced_search and its preview now accept connections_of_profile, a LinkedIn profile URL whose 1st-degree connections become the search audience. Combine it with the usual title, seniority, function, and company filters to mine a specific person’s network.
  • Personal email enrichment. Waterfall enrichment now supports personal_email as an enrichment_type on both the async and synchronous waterfall endpoints (single and bulk). Combine it with email and phone in a single call to retrieve professional email, personal email, and phone in one waterfall. Requests with personal_email (or phone) must include linkedin_url, and personal email enrichment requires per-user GDPR consent — without it, the API returns 422.
  • Scope phone lookups by country. All waterfall enrichment endpoints (sync, async single, and async bulk) now accept an optional phone_country_codes array. Pass ISO country codes to restrict phone results to specific regions and avoid spending credits on out-of-scope numbers.
  • Validation status on enriched emails. Contact responses now include email_status (and personal_email_status once a personal email is found) so you can see at a glance whether each address is valid, risky, or invalid without a separate verification call. Returned by GET /contacts/{id} and the synchronous waterfall.
  • Multiple phone numbers per contact. The phone field in waterfall responses is now an array of E.164-formatted strings, so contacts with several numbers no longer have results truncated to one.

​
Week of May 3, 2026

​
New features

  • Advanced lead search. The new POST /leads/advanced_search endpoint runs a full lead search from a structured filter set (titles, seniority, function, tenure, locations, industries, company size, signals, and more) and streams enriched leads to your webhook. No need to build a Sales Navigator URL yourself — Pronto translates the filters for you.
  • Search previews for leads and accounts. Validate filters and size an audience before kicking off a full run. The new preview endpoints return synchronously with the total estimated count plus the first 25 matches, and don’t consume credits or trigger webhooks:

​
Updates

  • Engagement counts on LinkedIn posts. Extract posts responses now include engagement_count, reactions_count, and comments_count for each post, so you can rank or filter content by traction without a second call.
  • More MCP tools. The Pronto MCP server now exposes advanced_search_leads for filter-based lead search, plus list management tools (create_list, get_lists, get_list, update_list) so AI assistants can build and update Sales Navigator lists on your behalf.

​
Week of April 26, 2026

​
New features

  • MCP server for AI assistants. Connect any MCP-compatible AI assistant — including Claude Desktop, Claude Code, and Cursor — directly to Pronto. Once installed, your assistant can find companies, search leads, and enrich contacts from a chat interface using your existing API key. See the MCP server guide for installation instructions and example prompts.
  • Search by saved Persona on Find People in Company. You can now pass a persona_id to the Find People in Company endpoint to drive a search from a Persona you’ve already defined in Pronto. When persona_id is provided, included and excluded job titles are taken from the saved Persona — no need to inline them in the request. Pass one or the other: combining persona_id with job_titles or excluded_job_titles returns a 422. See the Personas endpoints to list available Persona IDs.

​
Updates

  • More flexible people filters on Find People in Company. Find People in Company now accepts any one of job_titles, excluded_job_titles, functions, seniority_levels, included_locations, excluded_locations, or persona_id to satisfy the “at least one filter” requirement. Previously only job_titles or persona_id counted. Requests with none of these return 400.