Skip to main content

​
Overview

When an ID application is ready (all attachments have been signed and uploaded), the client can call this resource to flag the application as ready for approval. This will execute any automated onboarding procedures to analyze the application, and, if passing them, will take the identity to the approved state. They can also take the application to the rejected state, in case they find the information invalid.

​
HTTP request

POST /Agent/Legal/ReadyForApproval

​
Authentication

Requires a valid JWT bearer token.

​
Request (JSON)

{
	"keyId": Required(Str(PKeyId)),
	"legalId": Required(Str(PLegalId)),
	"nonce": Required(Str(PNonce)),
	"keySignature": Required(Str(PKeySignature)),
	"requestSignature": Required(Str(PRequestSignature))
}

​
Input parameters

ParameterDescription
PKeyIdIdentity of key to use for signing the Identity application.
PLegalIdIdentity of the Legal Identity to flag as ready for approval.
PNonceA unique random string, at least 32 characters long, with sufficient entropy to not be reused again. If reused, an error will be returned.
PKeySignatureCryptographic signature of the key ID, using the key password.
PRequestSignatureCryptographic signature of the requesut, using the account password.

​
Response (JSON)

{
	"Identity": Required(PIdentity)
}

​
Response parameters

ParameterDescription
PIdentityUpdated Identity object generated by the server.

​
Notes

This endpoint uses the request schema notation described in Pattern matching.