Skip to main content

​
Overview

Allows the client to add an attachment to a Legal Identity application.

​
HTTP request

POST /Agent/Legal/AddIdAttachment

​
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)),
	"attachmentBase64": Required(Str(PAttachmentBase64)),
	"attachmentFileName": Required(Str(PAttachmentFileName)),
	"attachmentContentType": Required(Str(PAttachmentContentType))
}

​
Input parameters

ParameterDescription
PKeyIdIdentity of key to use for signing the Identity application.
PLegalIdIdentity of the Legal Identity Application.
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.
PAttachmentBase64Base-64-encoding of attachment to add to the Identity application.
PAttachmentFileNameFile name of attachment.
PAttachmentContentTypeContent-Type of attachment.

​
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.