Explorer

Explorer provides a GraphQL workspace inside Studio. Enable the Explorer extension in configuration and open it from the app rail. Requests use the signed-in user’s project access.

Run your first read

1. Open Docs and inspect the query root generated for your deployed entities.
2. Build a small query selecting the record ID and only the fields you need.
3. Put parameter values in Variables as JSON.
4. Choose Execute and inspect Result, including any errors.
5. Compare the returned values with the saved record in Desk.

The schema is generated from your configuration. Local and relationship fields can have different shapes from global scalar fields. Use query examples and the current Docs panel rather than assuming a generic GraphQL schema.

Workspace controls

Explorer includes tabs, History, formatting, copying, and schema refresh. Refresh schema after a successful schema deployment if newly added fields are missing. History helps reuse operations, but avoid retaining secrets in literal query arguments.

Mutations

Mutations change actual project data. Start with reads, then use bounded mutation examples against development records. A mutation can return GraphQL errors even when the HTTP request completed, so inspect the response body.

A missing field or denied operation may reflect your role or spaces. See authentication and troubleshooting.