Skip to main content
GET
Get Requirements
Returns a live checklist of everything still required before the account’s application can be submitted: missing fields, missing documents and outstanding identity verifications. Use it to drive your own onboarding UI or to verify readiness before calling submit.

Example Request

Example Response

Business account

Individual account

Why an account is not ready

When readyToSubmit is false, submitBlocker names the reason — the same one Submit would return if you called it now. Check it instead of re-deriving the reason from the other fields.
Missing data is reported first. Once the application is complete and identity verification is the only hold, the code becomes KYC_INCOMPLETE:
For a business, details.unverified lists who is outstanding:
An account can have identityVerification: "verified" and still not be submittable — a passed identity check does not mean the application data is complete. submitBlocker is what tells the two apart.

Response Fields

A business must declare at least one beneficial owner or director. Until one is added, missingFields contains related_persons.

Authorizations

X-API-Key
string
header
required

Your Rolla API key

Path Parameters

accountId
string<uuid>
required

Identifier of an account owned by the same user as your API key's business

Response

Requirements retrieved successfully

success
boolean
Example:

true

message
string
Example:

"Requirements retrieved successfully"

data
object