Skip to main content
PUT
/
v1
/
onboarding
/
partner
/
applications
/
{applicationId}
/
sections
/
{sectionName}
Save section data for an application
curl --request PUT \
  --url https://api-sandbox.circle.com/v1/onboarding/partner/applications/{applicationId}/sections/{sectionName} \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{}'
{
  "data": {},
  "sections": [
    {
      "sectionName": "<string>"
    }
  ],
  "sectionsChanged": true
}

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.

Authorizations

​
Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

​
applicationId
string<uuid>
required

Application UUID

​
sectionName
string
required

Section name as returned by the schema (e.g. personal_information)

Body

application/json

Section field data matching the section's JSON Schema

Section data — structure varies by section. Consult GET /{applicationId}/schema.

Response

Saved section data with updated section statuses

​
data
object

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.

​
sections
object[]
​
sectionsChanged
boolean