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

# Submit field data in response to an UPDATE_FIELD or NEW_FIELD RFI



## OpenAPI

````yaml openapi/partner-openapi.yaml patch /v1/onboarding/partner/applications/{applicationId}/rfis/{rfiId}
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}/rfis/{rfiId}:
    patch:
      tags:
        - Partner RFIs
      summary: Submit field data in response to an UPDATE_FIELD or NEW_FIELD RFI
      operationId: updateRFIData
      parameters:
        - description: Application UUID
          example: 550e8400-e29b-41d4-a716-446655440000
          in: path
          name: applicationId
          required: true
          schema:
            type: string
            format: uuid
        - description: RFI UUID
          example: 550e8400-e29b-41d4-a716-446655440003
          in: path
          name: rfiId
          required: true
          schema:
            type: string
            format: uuid
      requestBody:
        content:
          application/json:
            schema:
              type: object
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RFIDataResponse'
          description: Field data saved and RFI marked as responded
        '400':
          description: Invalid request body or unsupported RFI type for this endpoint
        '401':
          description: Authentication required
        '403':
          description: Insufficient permissions
        '404':
          description: Application or RFI not found
        '422':
          description: Field value validation error
components:
  schemas:
    RFIDataResponse:
      type: object
      properties:
        data:
          type: object
          description: >-
            Current section field data after the update. Structure varies by
            application template.
        rfiId:
          type: string
          format: uuid
          description: The RFI that was responded to
        section:
          type: string
          description: Section name containing the updated field
  securitySchemes:
    bearerAuth:
      bearerFormat: JWT
      description: Bearer token obtained via Circle key exchange
      scheme: bearer
      type: http

````