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 Webhooks API

Subscription management for real-time signal callbacks — bulk create and delete up to 25 items per request, account-level HMAC-SHA256 secret with rotation, delivery test, contact opt-out notifications, and a delivery audit log with statistics.

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

Tagged areas include Webhook and Signals. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 11 operations across 9 paths, and defines 24 schemas. It is described by OpenAPI 3.2.0.

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

11 operations 9 paths 24 schemas 5 GET1 PATCH5 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 Webhooks 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 11

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

Webhooks 11

Subscribe to real-time notifications when contacts change jobs or companies experience key business events. Webhooks deliver HTTP POST requests to your endpoints when signals occu…

POST
/api/subscriptions
Create Subscription
createSubscription body → 201400401403500
GET
/api/subscriptions
List Subscriptions
listSubscriptions 2 params → 200400401500
GET
/api/subscriptions/{id}
Get Subscription by ID
getSubscriptionById 1 param → 200400404500
PATCH
/api/subscriptions/{id}
Update Subscription
updateSubscription 1 param body → 200400404500
POST
/api/subscriptions/{id}/test
Test Subscription
testSubscription 2 params → 200400401403404500
POST
/api/subscriptions/delete
Delete Subscriptions
deleteSubscriptions body → 200400401500
GET
/api/audit-logs
Get Audit Logs
getAuditLogs 4 params → 200400401500
GET
/api/audit-logs/stats
Get Audit Log Statistics
getAuditLogStats 1 param → 200401500
GET
/api/account/secret
Get Account Secret
getAccountSecret → 200401404500
POST
/api/account/secret/regenerate
Regenerate Account Secret
regenerateAccountSecret → 200401500
POST
/api/subscriptions/opt-out
Create Opt-Out Subscription
createOptOutSubscription body → 201400401403500

Schemas 24

The contract defines 24 schemas that model the data the API accepts and returns. The most detailed are SubscriptionWithoutSecret (11 properties), SubscriptionWithoutSecret_2 (11 properties), SubscriptionResponse_2 (10 properties), SubscriptionResponse (10 properties). Each schema is shown below with its type and property counts.

CreateSubscriptionRequest
object
3 properties 2 required
DeleteSubscriptionErrorResult
object
3 properties 3 required
AuditLogStatsResponse
object
4 properties 4 required
AuditLogsResponse
object
2 properties 2 required
DeleteSubscriptionResponse
object
4 properties 4 required
CreateOptOutSubscriptionRequest
object
Request body for creating an opt-out webhook subscription
3 properties 2 required
SubscriptionListResponse
object
2 properties 2 required
AuditLogEntry
object
9 properties 6 required
TestSubscriptionResponse
object
8 properties 5 required
ErrorResponse
object
3 properties 2 required
CreateSubscriptionErrorResult
object
3 properties 3 required
UpdateSubscriptionRequest
object
5 properties
CreateSubscriptionSuccessResult
object
3 properties 3 required
OptOutSubscriptionResponse
object
Response body returned when an opt-out subscription is created successfully
9 properties 8 required
CreateSubscriptionResponse
object
4 properties 4 required
SubscriptionResponse
object
10 properties
SubscriptionWithoutSecret
object
11 properties 8 required
DeleteSubscriptionSuccessResult
object
3 properties 3 required
PaginationResponse
object
4 properties 4 required
CreateSubscriptionRequest_2
object
3 properties 2 required
UpdateSubscriptionRequest_2
object
5 properties
SubscriptionResponse_2
object
10 properties
SubscriptionWithoutSecret_2
object
11 properties 8 required
PaginationResponse_2
object
4 properties 4 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

lusha-webhooks-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 Account API
Where this information came from

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