Skip to main content
PUT
Node.js
Required scope: merchants:write Use your institution’s credentials and keep your institution selected in the business headers. The businessId in the path identifies the business whose application you manage. Your institution must have managed-business access and an active relationship with that business. You can complete its application before that business is approved. Send the section’s complete saved answers in data. This replaces the section’s existing answers; omitted answers are removed. Read the current section first and include the answers you want to keep along with your changes. Before making changes, read the section list and send its exact updatedAt value, in quotes, as If-Match. Use the returned ETag for your next change. A missing or outdated required revision returns 409; fetch the latest application before trying again. The legalName-only JSON example illustrates a new company draft, not a completed section. Saving answers does not complete the section or submit the application for review.

Authorizations

Authorization
string
header
required

A user access token from sign-in. Send Authorization: Bearer followed by the token. Use this only on endpoints that list BearerAuth.

Headers

If-Match
string
required

The exact updatedAt value from the application's section list, enclosed in quotes. Required for applications you manage. A missing or outdated required value returns 409 without changing the draft.

X-Ledig-Business-Id
string

The business you are acting for. For a managed business, your institution must be authorised to act for it and API-key requests must use HMAC v2. Set this header explicitly; a business ID in the body does not select the business.

Minimum string length: 1
X-Ledig-Acting-Business-Id
string

Your institution's business ID when acting for a managed business. It must match your API key's owner or an institution you belong to. HMAC v2 signs the trimmed value, or an empty string when omitted.

Minimum string length: 1

Path Parameters

section
enum<string>
required
Available options:
company,
activity,
ownership,
regulation,
documents,
review
businessId
string
required

The managed business's ID. Keep your institution selected in the authentication headers.

Body

application/json
data
any
required

The answers for this section. Accepted fields and validation depend on the section.

Response

Section saved.

status
string
required
Allowed value: "success"
data
object
required
message
string