Skip to main content
POST
Each person carries your own clientPersonId, echoed back in the result, with every account you paid income into attached. It must be unique within the submission, and it is how you update or delete them later. Only persons with 15,000 EUR or more in income across their accounts are reportable. Send the optional Idempotency-Key header to make a retried batch safe.

Authorizations

Authorization
string
header
required

The access token received from the authorization server in the OAuth 2.0 flow.

Headers

Idempotency-Key
string

Client-provided idempotency key. UUID v4 suggested, max 255 characters. If provided, duplicate requests with the same key return the cached response.

Maximum string length: 255

Path Parameters

submissionId
string
required

Body

application/json
clientPersonId
string
required

Your own stable id for this person. Identifies them within the submission, so it must be unique across the persons you push, and it is how you address them on update and delete.

Maximum string length: 255
Example:

"CLIENT-000123"

accounts
object[]
required

List of accounts with the income paid into each of them

Required array length: 1 - 1000 elements
individual
object

The reportable natural person. Given instead of organisation.

organisation
object

The reportable legal entity. Given instead of individual.

Response

All persons saved

status
enum<string>
required
Available options:
SUCCESS,
FAILED
errors
object[]
required

Why the person was rejected. Empty when accepted.

clientPersonId
string

Your id for the person, echoed back to correlate this result with your record

Example:

"CLIENT-000123"

Last modified on September 1, 2026