Paedae · AsyncAPI Specification

Paedae Webhooks

Version

View Spec View on GitHub CompanyProximityLocationBeaconsGeofencingMobile SDKAdvertisingMarketingAsyncAPIEvents

AsyncAPI Specification

Raw ↑
generated: '2026-07-20'
method: searched
source: https://docs.gimbal.com/rest.html
type: Webhooks
provider: Paedae (Gimbal proximity platform)
summary: >-
  Gimbal delivers beacon/transmitter sighting events via HTTP POST callbacks to
  a configured action URL (the "Sightings Callback"). No AsyncAPI document is
  published by the provider.
webhooks:
  - name: Sightings Callback
    transport: http
    method: POST
    direction: outbound
    target: Customer-configured action URL
    description: >-
      Gimbal sends an HTTP POST to the configured action URL when a beacon or
      transmitter is sighted, arrived at, or departed from.
    trigger_events:
      - Arrived
      - Departed
      - Sighted
    payload_fields:
      - receiver identifier
      - transmitter identifier
      - triggering event (Arrived/Departed/Sighted)
      - dwell time
      - signal strength
      - location
      - battery level
      - timestamp
docs: https://docs.gimbal.com/rest.html

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.
All 92 tools →

Call it yourself

curl for this page
This AsyncAPI spec
curl "https://apis.io/api/v1/asyncapis/paedae-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.