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

Lusha Contact Filters API

Available filters for contact searches

Lusha Contact Filters API is one of 19 APIs that Lusha publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Contact Filters. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 5 operations across 5 paths, and defines 4 schemas. It is described by OpenAPI 3.2.0.

Requests are made against a single base URL, https://api.lusha.com.

5 operations 5 paths 4 schemas 4 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
Base URL
https://api.lusha.com
Authentication
API Key
Terms of Service
Resource Areas
1

Authentication & Security 1

Lusha Contact Filters API declares 1 security scheme for authenticating requests. An API key is passed in the header as api_key (ApiKeyAuth). By default, every request must be authenticated.

  • ApiKeyAuth — Your Lusha API key. You can find this in your Lusha dashboard under API settings. Include this key in the apikey header for all requests.

Paths & Operations 5

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

Contact Filters 5

Available filters for contact searches

GET
/prospecting/filters/contacts/departments
Departments
getContactDepartments → 200401
GET
/prospecting/filters/contacts/seniority
Seniority
getContactSeniority → 200401
GET
/prospecting/filters/contacts/existing_data_points
Data Points
getContactDataPoints → 200401
GET
/prospecting/filters/contacts/all_countries
Countries
getContactCountries → 200401
POST
/prospecting/filters/contacts/locations
Locations
searchContactLocations body → 200401

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are LocationFilter (5 properties), ErrorResponse (3 properties), CountryFilter (2 properties), LocationSearchRequest (1 property). Each schema is shown below with its type and property counts.

LocationSearchRequest
object
1 property 1 required
ErrorResponse
object
3 properties 2 required
CountryFilter
object
2 properties 2 required
LocationFilter
object
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

lusha-contact-filters-api-openapi.yml Raw ↑

Other APIs Lusha publishes across the network.

Lusha Search API
Lusha Enrich API
Lusha Search & Enrich API
Lusha Prospecting API
Lusha Lookalikes API
Lusha Buying Group API
Lusha Signals API
Lusha Website Visitors API
Lusha Filters API
Lusha Contacts Tables API
Lusha Companies Tables API
Lusha Webhooks API
Where this information came from

This is an independent, third-party profile of Lusha Contact Filters 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.