Glue · AsyncAPI Specification

Glue Outbound Webhooks

Version 1.0.0

Faithful AsyncAPI rendering of Glue's documented outbound webhook catalog. Webhooks are configured per OAuth Application; when a workspace authorizes the app, Glue creates a webhook posting to the app's URL. All requests are HTTPS and carry an X-Glue-Event-Signature header (HMAC-SHA256 of the body with the app secret). Non-200 responses are retried at 10s, 1m, and 10m.

View Spec View on GitHub CompanySoftware-as-a-ServiceTeam CommunicationMessagingCollaborationGraphQLWebhookMCPProductivityAI AgentsAsyncAPIEvents

Channels

outboundWebhook

Messages

messageCreated
Message created
A new message was sent in an existing thread. Contains the Message and its Thread.
threadCreated
Thread created
A new thread was created. Contains the Thread and the first Message.

AsyncAPI Specification

glue-webhooks-asyncapi.yml Raw ↑
generated: '2026-07-19'
method: generated
source: https://docs.glue.ai/developers/graphql-api/outbound_webhooks.md
spec_type: AsyncAPI
asyncapi: 3.0.0
info:
  title: Glue Outbound Webhooks
  version: 1.0.0
  description: >
    Faithful AsyncAPI rendering of Glue's documented outbound webhook catalog.
    Webhooks are configured per OAuth Application; when a workspace authorizes the
    app, Glue creates a webhook posting to the app's URL. All requests are HTTPS and
    carry an X-Glue-Event-Signature header (HMAC-SHA256 of the body with the app secret).
    Non-200 responses are retried at 10s, 1m, and 10m.
defaultContentType: application/json
channels:
  outboundWebhook:
    address: '{subscriberUrl}'
    parameters:
      subscriberUrl:
        description: The HTTPS URL registered on the OAuth Application.
    messages:
      messageCreated:
        $ref: '#/components/messages/messageCreated'
      threadCreated:
        $ref: '#/components/messages/threadCreated'
operations:
  receiveMessageCreated:
    action: receive
    channel:
      $ref: '#/channels/outboundWebhook'
    messages:
      - $ref: '#/channels/outboundWebhook/messages/messageCreated'
  receiveThreadCreated:
    action: receive
    channel:
      $ref: '#/channels/outboundWebhook'
    messages:
      - $ref: '#/channels/outboundWebhook/messages/threadCreated'
components:
  messages:
    messageCreated:
      name: message.created
      title: Message created
      summary: A new message was sent in an existing thread. Contains the Message and its Thread.
      payload:
        type: object
        properties:
          type: { type: string, const: message.created }
          workspaceID: { type: string }
          event:
            type: object
            properties:
              message: { type: object }
              thread: { type: object }
    threadCreated:
      name: thread.created
      title: Thread created
      summary: A new thread was created. Contains the Thread and the first Message.
      payload:
        type: object
        properties:
          type: { type: string, const: thread.created }
          workspaceID: { type: string }
          event:
            type: object
            properties:
              message: { type: object }
              thread: { type: object }

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/glue-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.