Hunter Leads Lists API
Manage leads list collections in Hunter.
Hunter Leads Lists 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 Lists. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a JSON-LD context, and 1 JSON Schema.
This API exposes 5 operations across 2 paths, and defines 3 schemas. It is described by OpenAPI 3.1.0, at version 2.0.0.
Requests are made against a single base URL, https://api.hunter.io/v2.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 3
Hunter Leads Lists 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 5
Across 2 paths, the API surfaces 5 operations — 1 DELETE, 2 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.
Manage leads list collections in Hunter.
Schemas 3
The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are LeadsList (4 properties), PaginationMeta (3 properties), Error (1 property). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Hunter 11
Other APIs Hunter publishes across the network.