Skip to main content
POST
Add Id Attachment

Overview

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

Authentication

Requires a valid JWT bearer token. Complete uploads while the application is Created, then call ReadyForApproval to start review. The server signs each attachment; no separate SignData call is needed. Follow the identity application guide for complete signed HTTP requests.

Notes

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

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Headers

Referer
string<uri>
required

Your application's HTTPS URL, for example https://app.example.com/. Include this header on every Agent API request, including backend calls, login, and account creation. Browser clients must use a referrer policy that sends the application origin. See /neuron-api/api-basics#required-referer-header.

Body

application/json
keyId
string
required

The signing key used for this identity application.

Identity.id of your application, which must still be in Created state.

nonce
string
required

A fresh random nonce of at least 32 characters. Do not reuse it.

keySignature
string
required

Base64 HMAC-SHA-256 of the key message using the key password. See the upload guide for the exact message.

requestSignature
string
required

Base64 HMAC-SHA-256 binding the file bytes, filename, content type, and legalId to the request. See the upload guide for the exact field order.

attachmentBase64
string
required

Base64-encoded file bytes, without a data URL prefix. Send one file per request.

attachmentFileName
string
required

Evidence filename recognized by the reviewer, such as ProfilePhoto.jpg or IdCardFront.png.

attachmentContentType
string
required

Media type matching the file bytes, such as image/jpeg or image/png.

Response

200 - application/json

Success

Identity
object
required