/graphql
Single multiplexed channel. The client and server exchange `graphql-transport-ws` control frames (`connection_init`, `subscribe`, `next`, `error`, `complete`, `ping`, `pong`) over this connection. Each active subscription is identified by a client-generated `id` and carries one of the supported GoldRush GraphQL subscription operations.
Channel address
Operations
Messages
application/jsonapplication/jsonapplication/jsonapplication/jsonapplication/jsonapplication/jsonapplication/jsonapplication/jsonAbout AsyncAPI
The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.
Browse every event-driven channel on the APIs.io network or compare with the broader Naftiko capability, Agent Skill, and MCP server surfaces of the same providers.