Skip to main content
POST
Submit Application
Validates that the account’s application is complete and submits it for compliance review. If anything is missing, the response lists exactly what’s outstanding.

Example Request

Example Response

Error Responses

When more than one thing is outstanding you get the most actionable one first: missing fields or documents are reported as 400 APPLICATION_INCOMPLETE and always list what is missing; 409 KYC_INCOMPLETE is returned only once the application data is complete and identity verification is the sole remaining hold.

Application incomplete (400)

Per-person entries are prefixed related_persons.<personId>., so you can tell which representative each one belongs to. Get Requirements reports the same list without attempting a submit. To find out what a submit would return without calling it, read submitBlocker on Get Requirements — it carries the same code and details as the errors below.

No beneficial owners declared (400)

Identity not verified — individual (409)

Key Behaviours

Individual accounts: the applicant must complete their KYC link before submission. Until they do, readyToSubmit is false and this endpoint returns 409 KYC_INCOMPLETE.
Business accounts: at least one beneficial owner or director must be declared, and every one of them must have completed identity verification. Generate KYC links for any unverified person — or, if you verify identity yourself, submit reliance for them — and retry once they finish.
Every related person needs a government identifiertaxId, or nin for Nigerian residents. It is not required when you add the person, only here at submission, where a missing one appears as related_persons.<personId>.taxId in missingFields. It can be patched onto an existing person with Update Related Person, so representatives added without one do not need re-creating. See the per-country formats.
Submitted applications are locked for editing. If the review team requests changes, the application reopens with a changes_requested status and a note explaining what to fix.

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

Application submitted successfully

success
boolean
Example:

true

message
string
Example:

"Application submitted successfully"

data
object