> ## Documentation Index
> Fetch the complete documentation index at: https://connectionshub.atlastube.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Solve Sheet

> Solve (or re-solve) a calculation sheet and return its results. Re-solving after an input update recomputes results on the same sheet; the sheet id does not change. Solving can take a few seconds, and is safe to retry — unchanged inputs produce the same results. The [Sheet Lifecycle guide](/templates/sheets-lifecycle) walks all four steps on one calculation.



## OpenAPI

````yaml api/openapi.json POST /v1/sheets/{sheetId}/solve
openapi: 3.1.0
info:
  title: Connections Hub API
  version: 1.0.0
  description: >-
    Run HSS Connections Hub calculators programmatically: create projects,
    create and solve sheets from any calculator template, run batches, and
    export reports to PDF.


    All endpoints require API key authentication.
servers:
  - url: https://api.calcs.com
security:
  - bearerAuth: []
tags:
  - name: Projects
    description: >-
      Create and manage calculation projects. Each user can have multiple
      projects to organize their calculations.
  - name: Sheets
    description: >-
      Manage individual calculation sheets — read one back, update its inputs,
      solve or re-solve it, and delete single sheets or clean up many at once.
  - name: Templates
    description: >-
      Run calculations using any enabled template. Supports all calculator types
      without requiring endpoint-specific code.
paths:
  /v1/sheets/{sheetId}/solve:
    post:
      tags:
        - Sheets
      summary: Solve Sheet
      description: >-
        Solve (or re-solve) a calculation sheet and return its results.
        Re-solving after an input update recomputes results on the same sheet;
        the sheet id does not change. Solving can take a few seconds, and is
        safe to retry — unchanged inputs produce the same results. The [Sheet
        Lifecycle guide](/templates/sheets-lifecycle) walks all four steps on
        one calculation.
      operationId: solve-sheet
      parameters:
        - name: Authorization
          in: header
          required: true
          example: Bearer YOUR_KEY_HERE
          schema:
            type: string
          description: >-
            The `Authorization` header is used to authenticate with the API
            using your API key. Value is of the format `Bearer YOUR_KEY_HERE`.
        - name: sheetId
          in: path
          required: true
          schema:
            type: string
            format: uuid
          description: >-
            Sheet UUID. Accepted in canonical, uppercase, braced, or
            unhyphenated form, as `projectId` is on `POST
            /v1/templates/{code}/sheets`.
      responses:
        '200':
          description: The sheet was solved and has results.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/SheetSolveResponse'
              examples:
                failing:
                  summary: Solved — the engineering check fails
                  value:
                    sheetId: 411435e9-85fd-4c2d-8876-a3efb3512559
                    projectId: 56b9335c-6859-4978-a6ec-33d780599c23
                    status: solved
                    passed: true
                    results:
                      A: 30.249999999999996
                      L: 18
                      P: 12.625481524365192
                      b: 5.5
                      …: 162 more
                    sheetUrl: >-
                      https://app.calcs.com/project/56b9335c-6859-4978-a6ec-33d780599c23/sheet/411435e9-85fd-4c2d-8876-a3efb3512559
                    summaryCheck: false
                    summaryCheckReferenceId: f_c
                    summaryCheckError: false
                    summaryCheckFailReasons:
                      - >-
                        Applied compressive stress must be less than the elastic
                        buckling stress.
                    summaryCheckStatus: fail
        '400':
          description: The sheetId path parameter is not a valid UUID.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ValidationError'
              examples:
                non_uuid_sheet_id:
                  summary: sheetId is not a UUID
                  value:
                    error:
                      code: VALIDATION_ERROR
                      message: sheetId must be a UUID.
        '401':
          description: Unauthorized — missing or invalid API key.
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/ProblemDetails'
              examples:
                unauthorized:
                  summary: Missing or invalid API key
                  value:
                    type: https://httpproblems.com/http-status/401
                    title: Unauthorized
                    status: 401
                    detail: No Authorization Header
                    instance: /v1/sheets/84cb248b-a36f-41a9-9639-575bc597341e/solve
                    trace:
                      timestamp: '2026-07-22T07:19:15.570Z'
                      requestId: 0a2d7511-aa02-45b6-86ce-1bb19c0486a2
                      buildId: 75f93f77-18bc-4f82-9a77-2e322a1bba58
                      rayId: a1f0ad123af1e6b3
        '404':
          description: The sheet does not exist, or is not accessible with this API key.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              examples:
                not_found:
                  summary: Sheet does not exist, or is not accessible with this API key
                  value:
                    error:
                      code: NOT_FOUND
                      message: Sheet not found.
        '422':
          description: >-
            The solve completed without producing results, or the sheet cannot
            be modified (e.g. its project is archived).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              examples:
                no_results:
                  summary: The solve produced no results
                  value:
                    error:
                      code: CALCULATION_ERROR
                      message: >-
                        Calculation produced no results. This usually means
                        required inputs are missing, or none of the template's
                        outputs applied to them.
                cannot_modify:
                  summary: The sheet cannot be modified
                  value:
                    error:
                      code: VALIDATION_ERROR
                      message: >-
                        The sheet cannot be modified. Check that its project is
                        not archived.
      security:
        - api_key: []
components:
  schemas:
    SheetSolveResponse:
      type: object
      description: >-
        Results of solving the sheet. Re-solving after an input update refreshes
        results on the same sheet.
      properties:
        sheetId:
          type: string
          format: uuid
          description: Unique identifier for the sheet.
        projectId:
          type: string
          format: uuid
          description: Project the sheet belongs to.
        status:
          type: string
          enum:
            - solved
            - unsolved
          description: >-
            `solved` when the results below were computed from the inputs the
            sheet holds now — the normal outcome. `unsolved` only where another
            write landed on the sheet while the solve was running, leaving
            results that no longer match its inputs; solve again to get results
            for them.
        passed:
          type:
            - boolean
            - 'null'
          deprecated: true
          description: >-
            Deprecated: read `summaryCheckStatus` for the verdict of this solve.
            `passed` is not this solve's verdict: a failing calculation can
            report `true`, even on its first solve, or `null`.
        summaryCheck:
          type:
            - number
            - boolean
          description: >-
            Value of the template's governing check for this solve. Absent when
            the check could not be evaluated (`summaryCheckStatus` is `error`).
            A template that defines no governing check reports `true` here, so
            read the verdict from `summaryCheckStatus`, which tells the two
            apart (`not_evaluated`).
        summaryCheckReferenceId:
          type: string
          description: Reference ID of the widget `summaryCheck` came from.
        summaryCheckError:
          type: boolean
          description: >-
            Whether the governing check could not be evaluated. A check in error
            has no verdict, whatever `summaryCheck` holds.
        summaryCheckFailReasons:
          type: array
          items:
            type: string
          description: Why the governing check failed, when it did.
        summaryCheckStatus:
          type: string
          enum:
            - pass
            - fail
            - error
            - not_evaluated
          description: >-
            Verdict of the template's governing check for this solve. `pass`:
            the check passed (`summaryCheck` is `true`, or a number from 0 to
            1). `fail`: the check evaluated and failed (`false`, or a number
            outside 0 to 1). `error`: the check could not be evaluated —
            `summaryCheckError` is `true`, or the solve produced no value for a
            check the template defines; treat it as not passing.
            `not_evaluated`: the template defines no governing check.
        results:
          type: object
          additionalProperties: true
          description: >-
            Solved outputs, keyed by the reference IDs the template schema lists
            in `outputs[]`. A given solve returns the subset of those that apply
            to the inputs you sent.
        sheetUrl:
          type: string
          format: uri
          description: Link to the sheet in the Calcs.com app.
      required:
        - sheetId
        - status
        - passed
        - results
        - sheetUrl
    ValidationError:
      type: object
      description: Validation error response for invalid API inputs
      properties:
        error:
          type: object
          properties:
            code:
              type: string
              enum:
                - VALIDATION_ERROR
              description: Error code for validation failures
            message:
              type: string
              description: Human-readable error summary
              example: Input validation failed
            details:
              type: array
              description: Array of specific validation errors
              items:
                type: object
                properties:
                  field:
                    type: string
                    description: Path to the invalid field (e.g., 'L_X', 'supports.0.2')
                  message:
                    type: string
                    description: Description of what's wrong with the field
                required:
                  - field
                  - message
          required:
            - code
            - message
      required:
        - error
      example:
        error:
          code: VALIDATION_ERROR
          message: Input validation failed
          details:
            - field: L_X
              message: Expected number, received string
            - field: supports
              message: At least 2 supports are required
    ProblemDetails:
      type: object
      description: >-
        RFC 7807 (`application/problem+json`) error returned by the API gateway
        before a request reaches the handler — currently authentication failures
        (401). Note this differs from the `{ error: { code, message, details }
        }` envelope returned by the handler for validation and not-found errors.
      properties:
        type:
          type: string
          format: uri
          description: URI identifying the problem type.
        title:
          type: string
          description: Short, human-readable summary of the problem type.
        status:
          type: integer
          description: HTTP status code.
        detail:
          type: string
          description: Human-readable explanation specific to this occurrence.
        instance:
          type: string
          description: The request path that produced the error.
        trace:
          type: object
          description: >-
            Gateway trace metadata for support (timestamp, requestId, buildId,
            rayId).
      required:
        - type
        - title
        - status
        - detail
    ErrorResponse:
      type: object
      description: >-
        Standard error envelope for handler errors. `code` is a stable
        machine-readable error code (e.g. NOT_FOUND, UPSTREAM_ERROR); `message`
        is human-readable and may change.
      properties:
        error:
          type: object
          properties:
            code:
              type: string
              description: Machine-readable error code.
            message:
              type: string
              description: Human-readable error message.
          required:
            - code
            - message
      required:
        - error
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: >-
        Send your API key as a bearer token: `Authorization: Bearer
        YOUR_API_KEY`. Every endpoint requires one.
    api_key:
      type: http
      scheme: bearer

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.