Workbench (Apollo Sandbox)
Wetel’s GraphQL API ships with a built-in interactive workbench: Apollo Sandbox. It’s a browser-based GraphQL IDE that’s available the moment you point a browser at the API endpoint — no extra sign-up, no separate tool to install.
Where it is
Section titled “Where it is”Open https://api.wetel.dev/graphql in a browser. You’ll land directly in Apollo Sandbox, connected to the live Wetel API.
Authenticating inside Sandbox
Section titled “Authenticating inside Sandbox”Sandbox doesn’t handle login for you — you authenticate the same way any API client does, by attaching credentials to your requests. In the Sandbox UI, open the headers panel (usually along the bottom or side of the operation editor) and add either:
Authorization: Bearer <your JWT>, or- your API key header, depending on which auth method you’re using.
See Authentication for how to obtain a JWT or API key — this page assumes you already have one and just covers using it inside Sandbox.
What you can do with it
Section titled “What you can do with it”- Run any query or mutation by hand. Write an operation, fill in variables, hit run, and see the raw response — useful for confirming a call behaves the way you expect before wiring it into real client code.
- Browse the full schema. Sandbox’s built-in docs panel is generated from live introspection, so it always reflects the current API — every type, field, argument, and description is browsable without leaving the page. This is a good complement to the API Reference when you want to explore interactively rather than read linearly.
- Prototype quickly. Because Sandbox validates your query against the live schema as you type, it’s a fast way to sanity-check field names and argument shapes before committing to code.
Limitation: no live subscription visualization
Section titled “Limitation: no live subscription visualization”Sandbox can execute queries and mutations, but it is not a good tool for watching subscription or streaming events as they arrive — it isn’t built to visualize a long-lived event stream the way it visualizes a single request/response. If you need to observe real-time events (message deltas, session state changes, and so on), see Events & Subscriptions for how those work, and consider writing a small test script (a short Node or Python snippet using a GraphQL WebSocket client) instead of relying on Sandbox for that part of your testing.