Create individual
POST/service/individual
Creates an individual for the organisation, to onboard an existing or a new user. No field is mandatory, and an unknown field gives HTTP 400. With an email, the service also makes a login account for the individual; an e-mail address that already has an account gives HTTP 400. An externalId or a mapperId that another individual has gives HTTP 409.
Request
- application/json
Body
individual object
Shallowly models an Individual which may reference some instance in an external system (registration system, functional ID, foundational ID etc). An Individual instance of this model is not to be mistaken with a unique natural individual. It is up to the system owner to decide if this record permits mapping to a natural individual and/or if a single Individual row can map to several consent agreements.
The unique ID of an Individual row.
Reference to another foundational/functional ID, which is likely PII
External ID type specifier. A string. For instance "email" or "foundational ID". Can be used in later queries.
This could be an FK, but for now we do not have a mapping of identity providers. IDBB may have more requirements.
Name of the individual
The identifier of the login account of the individual. The service sets it when the individual has an email.
The e-mail address. With an e-mail address, the service also makes a login account for the individual.
Phone
Device token of the individual
Possible values: [android, ios]
Device type(OS) of the individual
Defines the mapper id of the individual
Responses
- 200
- 400
- 401
- 409
- 500
Individual created successfully
Response Headers
- application/json
- Schema
- Example (from schema)
Schema
individual object
Shallowly models an Individual which may reference some instance in an external system (registration system, functional ID, foundational ID etc). An Individual instance of this model is not to be mistaken with a unique natural individual. It is up to the system owner to decide if this record permits mapping to a natural individual and/or if a single Individual row can map to several consent agreements.
The unique ID of an Individual row.
Reference to another foundational/functional ID, which is likely PII
External ID type specifier. A string. For instance "email" or "foundational ID". Can be used in later queries.
This could be an FK, but for now we do not have a mapping of identity providers. IDBB may have more requirements.
Name of the individual
The identifier of the login account of the individual. The service sets it when the individual has an email.
The e-mail address. With an e-mail address, the service also makes a login account for the individual.
Phone
Device token of the individual
Possible values: [android, ios]
Device type(OS) of the individual
Defines the mapper id of the individual
{
"individual": {
"id": "64541a2e6e7569000145cd66",
"externalId": "[email protected]",
"externalIdType": "email",
"identityProviderId": "64541a2e6e7569000145ab12",
"name": "string",
"iamId": "string",
"email": "string",
"phone": "string",
"pushNotificationToken": "string",
"deviceType": "android",
"mapperId": "string"
}
}
bad input parameter
Response Headers
Unauthorized
Response Headers
- application/json
- Schema
- Example (from schema)
Schema
{
"errorCode": 400,
"errorDescription": "Bad input parameter"
}
Another individual of the organisation has the same externalId or mapperId.
Response Headers
- application/json
- Schema
- Example (from schema)
Schema
{
"errorCode": 400,
"errorDescription": "Bad input parameter"
}
Internal server error
Response Headers
- application/json
- Schema
- Example (from schema)
Schema
{
"errorCode": 400,
"errorDescription": "Bad input parameter"
}