How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Hunter

Hunter Leads API

Manage leads stored in Hunter.

Documentation Provider Profile APIs.io OpenAPI GitHub

Hunter Leads API is one of 12 APIs that Hunter publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 1 JSON Schema definition.

Tagged areas include Leads. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a JSON-LD context, and 1 JSON Schema.

This API exposes 6 operations across 2 paths, and defines 5 schemas. It is described by OpenAPI 3.2.0, at version 2.0.0.

Requests are made against a single base URL, https://api.hunter.io/v2.

6 operations 2 paths 5 schemas 1 DELETE2 GET1 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0.0
Base URL
https://api.hunter.io/v2
Authentication
API Key, API Key, HTTP Bearer
Contact
Hunter Support
License
Proprietary
Terms of Service
View terms
Resource Areas
1

Authentication & Security 3

Hunter Leads API declares 3 security schemes for authenticating requests. An API key is passed in the query as api_key (apiKeyQuery). An API key is passed in the header as X-API-KEY (apiKeyHeader). It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • apiKeyQuery — API key passed as a query parameter.
  • apiKeyHeader — API key passed via the X-API-KEY header.
  • bearerAuth — API key passed as a Bearer token in the Authorization header.

Paths & Operations 6

Across 2 paths, the API surfaces 6 operations — 1 DELETE, 2 GET, 1 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

Leads 6

Manage leads stored in Hunter.

GET
/leads
Hunter List Leads
listLeads 9 params → 200401429
POST
/leads
Hunter Create Lead
createLead body → 201400401422
PUT
/leads
Hunter Create or Update Lead
upsertLead body → 200201400401422
GET
/leads/{id}
Hunter Get Lead
getLead 1 param → 200401404
PUT
/leads/{id}
Hunter Update Lead
updateLead 1 param body → 200400401404422
DELETE
/leads/{id}
Hunter Delete Lead
deleteLead 1 param → 204401404

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are Lead (22 properties), LeadInput (15 properties), PaginationMeta (3 properties), VerificationStatus (2 properties). Each schema is shown below with its type and property counts.

LeadInput
object
15 properties
PaginationMeta
object
3 properties
Error
object
1 property
Lead
object
22 properties
VerificationStatus
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

hunter-leads-api-openapi.yml Raw ↑

Other APIs Hunter publishes across the network.

Hunter Account API
AE Profile APIs.io
Hunter Campaigns API
AE Profile APIs.io
Hunter Combined Enrichment API
AE Profile APIs.io
Hunter Company Enrichment API
AE Profile APIs.io
Hunter Discover API
AE Profile APIs.io
Hunter Domain Search API
AE Profile APIs.io
Hunter Email Count API
AE Profile APIs.io
Hunter Email Enrichment API
AE Profile APIs.io
Hunter Email Finder API
AE Profile APIs.io
Hunter Email Verifier API
AE Profile APIs.io
Hunter Leads Lists API
AE Profile APIs.io
#Leads
← Back to H APIs
API Details
ID
hunter:hunter-leads-api
Base URL
https://api.hunter.io/v2
Docs
https://hunter.io/api-documentation/v2#leads
Provider
Hunter
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=hunter-leads-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/hunter-leads-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Hunter Leads API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.