Skip to main content
POST
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. This is available for individual beneficial owners who require verification on the submitted application. It is not available for every shareholder or for people from another application. Use the returned short-lived verification access promptly; do not cache or log it.

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

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

ownerId
string
required
businessId
string
required

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

Response

Temporary access for completing the identity check. Do not cache or log this response.

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