GraphQL Subscription Tester (WebSocket)
Run GraphQL subscriptions against any server using graphql-ws or the legacy Apollo protocol. Your browser connects directly — nothing is proxied.
Help shape GraphQL Subscription Tester (WebSocket)
The bug you just noticed will fade in 3 minutes. The feature idea will vanish after your next tab switch. Crazy peps don't suffer silently.
Frequently Asked Questions
The modern graphql-transport-ws protocol used by graphql-ws, Apollo Server 3+, Hasura, Yoga and Hot Chocolate, and the legacy subscriptions-transport-ws protocol (subprotocol “graphql-ws”) used by Apollo Server 2.
Put your token in the connection_init payload, e.g. {"authorization": "Bearer {{token}}"}. It is sent before any subscription, like connectionParams in client libraries.
The tester reconnects with backoff and automatically re-subscribes every operation that was still running, just like production clients.
Yes. Each operation gets its own id and appears as a chip with its result count and a Stop button. Filter the log by operation name to follow one stream.
No. The WebSocket goes straight from your browser to your GraphQL endpoint. Queries, variables and tokens never pass through our servers.