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

# Get the JSON Schema (draft 2020-12) for an application's template



## OpenAPI

````yaml openapi/partner-openapi.yaml get /v1/onboarding/partner/applications/{applicationId}/schema
openapi: 3.1.0
info:
  description: >
    Partner-facing API for programmatic onboarding. Use these endpoints to
    create and

    manage onboarding applications on behalf of your customers, submit sections
    of data,

    upload supporting documents, and respond to Requests for Information (RFIs).


    ## Authentication

    All endpoints require a Bearer token obtained via the Circle key exchange.
    Include the

    token in the `Authorization: Bearer <token>` header.


    ## Idempotency

    All POST endpoints require an `X-Idempotency-Key` header. Provide a
    client-generated UUID v4

    with each POST request. If the same key is retried, the original response is
    returned without

    re-executing the operation. Omitting the header on a POST will result in a
    400 error.
  title: Circle Partner Onboarding API
  version: '2026-04-15'
servers:
  - description: Production
    url: https://api.circle.com
  - description: Sandbox
    url: https://api-sandbox.circle.com
security:
  - bearerAuth: []
paths:
  /v1/onboarding/partner/applications/{applicationId}/schema:
    get:
      tags:
        - Partner Applications
      summary: Get the JSON Schema (draft 2020-12) for an application's template
      operationId: getApplicationSchema
      parameters:
        - description: Application UUID
          example: 550e8400-e29b-41d4-a716-446655440000
          in: path
          name: applicationId
          required: true
          schema:
            type: string
            format: uuid
        - description: >-
            When true, prune sections and conditional fields that definitively
            do not apply to the application's saved data and add a top-level
            "x-resolved": true marker. Indeterminate branches (parent field not
            yet saved) are kept. Defaults to false (the full canonical schema).
          in: query
          name: resolved
          schema:
            type: boolean
            default: false
      responses:
        '200':
          content:
            application/json:
              schema:
                type: object
                description: >-
                  A JSON Schema document whose structure varies by application
                  template.
          description: >-
            JSON Schema (draft 2020-12) describing the required fields for this
            application's template
        '401':
          description: Authentication required
        '403':
          description: Insufficient permissions
        '404':
          description: Application not found
components:
  securitySchemes:
    bearerAuth:
      bearerFormat: JWT
      description: Bearer token obtained via Circle key exchange
      scheme: bearer
      type: http

````