> ## 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.

# Save data for multiple sections in a single request

> Accepts a JSON object keyed by section name. Each value is the same payload shape as PUT /sections/{sectionName}. Validation is atomic: all sections are validated before any data is saved, and if any section fails validation the entire request is rejected. Saves are sequential: after validation passes, sections are persisted one at a time. Array sections use upsert semantics: items with refId update existing entities, items without refId create new entities. Existing entities not included are preserved. The response data field is an object keyed by section name containing the saved data for each section.



## OpenAPI

````yaml openapi/partner-openapi.yaml patch /v1/onboarding/partner/applications/{applicationId}/data
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}/data:
    patch:
      tags:
        - Partner Applications
      summary: Save data for multiple sections in a single request
      description: >-
        Accepts a JSON object keyed by section name. Each value is the same
        payload shape as PUT /sections/{sectionName}. Validation is atomic: all
        sections are validated before any data is saved, and if any section
        fails validation the entire request is rejected. Saves are sequential:
        after validation passes, sections are persisted one at a time. Array
        sections use upsert semantics: items with refId update existing
        entities, items without refId create new entities. Existing entities not
        included are preserved. The response data field is an object keyed by
        section name containing the saved data for each section.
      operationId: bulkSave
      parameters:
        - description: Application UUID
          example: 550e8400-e29b-41d4-a716-446655440000
          in: path
          name: applicationId
          required: true
          schema:
            type: string
            format: uuid
      requestBody:
        content:
          application/json:
            schema:
              type: object
              description: >-
                Section data keyed by section name — structure varies by
                template. Consult GET /{applicationId}/schema.
        description: >-
          JSON object keyed by section name. Each value matches the section's
          JSON Schema.
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/SectionSaveResponse'
          description: All section statuses after save
        '400':
          description: Invalid request (unknown section, empty payload)
        '401':
          description: Authentication required
        '403':
          description: Insufficient permissions
        '404':
          description: Application not found
        '409':
          description: Application is not in an editable state
        '422':
          description: Validation error
components:
  schemas:
    SectionSaveResponse:
      type: object
      properties:
        data:
          type: object
          description: >-
            Saved section field data — structure varies by application template.
            For single-section saves this is the section payload directly. For
            bulk saves this is an object keyed by section name. Retrieve the
            shape via GET /{applicationId}/schema.
        fieldsChanged:
          type: boolean
        sections:
          type: array
          items:
            $ref: '#/components/schemas/ApplicationSectionSummary'
        sectionsChanged:
          type: boolean
    ApplicationSectionSummary:
      type: object
      properties:
        sectionName:
          type: string
        status:
          type: string
          enum:
            - action_required
            - complete
            - incomplete
            - not_started
  securitySchemes:
    bearerAuth:
      bearerFormat: JWT
      description: Bearer token obtained via Circle key exchange
      scheme: bearer
      type: http

````