GraphQL Response Analyzer

A GraphQL Response is a JSON document returned by a GraphQL server following the execution of a query, mutation, or subscription. Unlike traditional REST API endpoints that emit varying response schemas and rely solely on coarse HTTP status codes (such as 200, 400, 404, or 500), the GraphQL specification establishes a strict top-level response envelope.

A GraphQL response may contain a data map, an errors list, and an optional extensions map. Because individual GraphQL resolvers execute independently, a response can succeed partially—returning requested data for healthy resolvers while simultaneously cataloging granular errors for failed resolvers.

According to Section 7 of the official GraphQL Specification, a valid response document contains up to three standardized top-level keys:

One of the most important architectural features of GraphQL is Partial Execution Resilience. In REST APIs, an unhandled database exception on an auxiliary relationship (such as user comments or billing status) typically fails the entire HTTP request with a 500 Internal Server Error.

In GraphQL, field resolvers run asynchronously. If a field is defined as nullable (e.g. email: String rather than String!) and its downstream service fails, GraphQL sets email: null in the data object, appends an error object to errors, and returns the rest of the user data intact.

Null values in GraphQL can represent legitimate empty fields or silent resolver failures. The analyzer tracks:

• Total Null Count & Percentage: The proportion of response fields that evaluated to null.
• Null Paths Roster: Exact JSONPaths for every null field with one-click editor navigation.
• Null-Error Correlation: Identifies which null fields correspond directly to entries in the errors list.

The Tree Explorer converts large GraphQL JSON documents into an interactive, expandable tree. Developers can search across keys, values, and paths, expand/collapse sub-trees, and click any node to immediately reveal its exact line in the editor.

When diagnosing large responses containing thousands of lines, manually locating a failed field is tedious. ToolMono's location engine maps JSON pointers and GraphQL error paths directly to line and column coordinates in the editor, scrolling and highlighting the exact target with a single click.

Consider this partial response from an e-commerce API:

{
  "data": {
    "user": {
      "id": "usr_100",
      "name": "Jane Doe",
      "email": null
    }
  },
  "errors": [
    {
      "message": "Email service unavailable",
      "path": ["user", "email"],
      "extensions": {
        "code": "SERVICE_UNAVAILABLE"
      }
    }
  ]
}

Analysis Summary:

• Classification: PARTIAL RESPONSE.
• Resolved Fields: user.id and user.name are present.
• Failed Resolver: user.email failed and bubbled to null.
• Error Code: SERVICE_UNAVAILABLE (Category: Server / Resolver).

Generate comprehensive documentation for pull requests, bug reports, and incident reviews. Export complete audit summaries as Markdown or machine-readable JSON with one click.