canonical: https://jentic.com/apis/evaboot.com/evaboot # Evaboot Public API The Evaboot Public API extracts leads from Sales Navigator and enriches them with verified contact details. You can start extraction jobs from a search URL or a single profile, find and validate professional email addresses, build search queries, and check your remaining quota. Jobs run asynchronously, so you start a job and read its result by id. ## For AI agents Extract leads from Sales Navigator, find and validate professional emails, build search queries, and check quota through the Evaboot Public API. Jobs are started and then polled by id. ## Scope Covers lead extraction, email finding, and email validation. Does not send outreach, manage CRM records, or run marketing campaigns. ## Capabilities - Start a lead extraction from a Sales Navigator search URL - Extract a single lead from a profile - List and retrieve extraction jobs by id - Find professional email addresses for leads - Validate email addresses for deliverability - Check the remaining account quota ## Use cases ### AI Agent Lead Extraction An AI agent can turn a Sales Navigator search into a structured lead list by starting an extraction job and reading its result. Through Jentic the agent finds the extraction operation by intent and passes the search URL, then polls the job by id, so a sales assistant can build prospect lists without a developer wiring the endpoints by hand. Example prompt: Start an extraction from a Sales Navigator search URL, then poll the job and return the extracted leads ### Email Finding and Verification A prospecting agent can attach verified email addresses to leads by running the email finder and then validating the results. The API finds professional emails and checks deliverability, so an agent can produce a clean, contactable list and drop addresses that would bounce. Example prompt: Find an email for a lead, validate it, and return the address only if it is deliverable ### Quota-Aware Batch Enrichment An operations agent can enrich lead lists at scale while staying inside plan limits. The API reports remaining quota and lets an agent start batch email-finder and validation jobs, so a workflow can check the budget before spending it and pace enrichment across runs. Example prompt: Check the remaining quota, then start an email-finder job only if enough credits are available ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/v1/extractions/url/` | Start an extraction from a search URL | | POST | `/v1/extractions/single/` | Extract a single lead from a profile | | GET | `/v1/extractions/` | List extraction jobs | | GET | `/v1/extractions/{extraction_id}/` | Get an extraction job by id | | POST | `/v1/email-finder/` | Start an email-finder job | | GET | `/v1/email-finder/{job_id}/` | Get an email-finder job by id | | POST | `/v1/email-validation/` | Start an email-validation job | | GET | `/v1/quota/` | Check the remaining account quota | ## Key resources - **Extractions** — Start lead extractions from a search URL or profile and read their results by id - **Email Finder** — Find professional email addresses for leads and poll job results - **Email Validation** — Validate email addresses for deliverability and poll job results - **Quota** — Check the remaining account quota before starting jobs ## Why Jentic - **Setup:** Wiring Evaboot by hand means managing an API token, sending it as a bearer token on every request, and coordinating the start-and-poll pattern for asynchronous jobs. Through Jentic you install once, import Evaboot from the API Directory, store the token once, and your agent calls it. - **Permission scoping:** You decide which Evaboot operations the agent may use. Allow it to check quota and read results while blocking credit-spending jobs, and because job ids sit in the URL path, a rule can restrict it to specific jobs so it cannot start work you did not approve. - **Credential handling:** Your Evaboot API token is stored encrypted by your own Jentic One instance and injected as a bearer token at execution time. It never enters the agent's prompt, logs, or context window. - **Discovery method:** Agents search Jentic by intent such as 'extract leads' or 'validate an email', and Jentic returns the matching Evaboot operation with its input schema so the agent calls the right endpoint. ## Related APIs - **Hunter** — Hunter finds and verifies professional email addresses by domain. - **Apollo** — Apollo provides a large B2B contact database with search and enrichment. - **Clearbit** — Clearbit enriches contacts and companies with firmographic data. ## FAQ ### Is there an Evaboot MCP server? You don't need an MCP server to give your agent the Evaboot Public API. Jentic connects it directly from the API Directory: import it, store your token once, and your agent can extract leads and validate emails. Operations are discovered on demand, so no extra tool definitions sit in the agent's context. ### Can I limit what my agent is allowed to do with the Evaboot Public API? Yes. You choose which operations the agent may call, so you can allow it to check quota and read extraction results without starting new jobs that spend credits. Because job ids appear in the URL path, a rule can also pin the agent to specific jobs, and every call is logged. ### What authentication does the Evaboot Public API use? The Evaboot Public API authenticates with a bearer token, sent in the Authorization header per its OpenAPI spec. Through Jentic the token is stored encrypted by your own Jentic One instance and added to each request at call time, so it never appears in the agent's prompt or logs. ### Can my agent find and verify a lead's email with the Evaboot Public API? Yes. The agent can start an email-finder job for a lead and then run email validation on the result to confirm deliverability. Because jobs run asynchronously, the agent starts a job and reads its outcome by id before returning the address. ### What are the rate limits for the Evaboot Public API? The OpenAPI spec does not specify rate limits, but jobs consume account credits. Check the Evaboot documentation at https://evaboot.com for current quota and request limits, and read the quota operation before starting large batches. ### How do I extract leads through Jentic? Search Jentic for 'extract leads from Sales Navigator', import the Evaboot operation, and store your token once. Your agent then starts extraction jobs and reads their results on demand. To run it on your own infrastructure, install Jentic One from its GitHub repo.