Divshot · AsyncAPI Specification
Divshot Webhooks
Version
View Spec
View on GitHub
CompanyWeb HostingStatic HostingFrontendDeploymentDeveloper ToolsDefunctAcquiredAsyncAPIEvents
AsyncAPI Specification
generated: '2026-07-20'
method: searched
source: https://github.com/divshot/divshot-api/blob/master/README.md
type: Webhooks
status: abandoned
asyncapi_published: false
notes: >-
Divshot documented a per-app webhook management surface in its first-party API
client and CLI. No AsyncAPI document, no event-name catalog, and no payload
schemas were ever published, and the service is defunct - so only the
management surface is recorded here. Nothing about the event payloads is
inferred.
management:
scope: per-app
fields_documented:
- name: url
description: Destination URL the webhook posts to
- name: active
description: Whether the webhook is enabled
operations:
- name: list
source: app.webhooks.list()
- name: create
source: 'app.webhooks.create({url, active})'
- name: pause
source: app.webhooks.pause(hook)
- name: resume
source: app.webhooks.resume(hook)
- name: remove
source: app.webhooks.remove(hookId)
cli:
- hooks
- hooks:add
- hooks:remove
- hooks:pause
- hooks:resume
events:
catalog_published: false
known_events: []
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/divshot-webhooks"
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.