Lugg · AsyncAPI Specification
Lugg Webhooks Asyncapi
Version
View Spec
View on GitHub
CompanyLogisticsDeliveryMovingLast MileTransportationOn-DemandWebhookAsyncAPIEvents
AsyncAPI Specification
generated: '2026-07-20'
method: searched
source: https://docs.lugg.com
spec_type: Webhooks
docs: https://docs.lugg.com
summary: >-
The Lugg API publishes a webhook event surface. The reference at docs.lugg.com
exposes an "Integrations" tag group with a "Webhook endpoints" resource for
registering and managing webhook endpoints, plus a "webhook" navigation node.
This captures the confirmed existence of the webhook surface; the individual
event types and payload schemas render client-side in the Scalar reference and
were not machine-extractable in this pass — capture them verbatim on the next
run that can read the underlying OpenAPI document. No AsyncAPI document is
published; this is a webhook (HTTP callback) surface.
webhooks:
management:
resource: Webhook endpoints
operations_documented: true
notes: >-
CRUD-style management of webhook endpoint registrations under the
Integrations tag group.
events: []
events_note: >-
Event catalog not extractable from the server-rendered reference in this
pass; not fabricated.
Work with this as data
Every AsyncAPI spec here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for asyncapi
4 MCP tools reach this
find_asyncapisBrowse and filter every AsyncAPI spec in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This AsyncAPI spec
curl "https://apis.io/api/v1/asyncapis/lugg-webhooks-asyncapi"
All asyncapi
curl "https://apis.io/api/v1/asyncapis?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.