2026-11-16
Summary: Persons can be updated with a social security number and a birth name, also persons with only subsidy application roles
Persons
New Update Types
POST /persons/{person_id}/updates accepts two new types:
social_security_number- Set or replace the person's social security number or, if the person has none, the subsidy number (Zulagenummer)birth_name- Set or replace the person's birth name
You can replace a value that is set, but you cannot remove it. GET /persons/{person_id}/updates and GET /persons/{person_id}/updates/{update_id} return the new types.
Updates for Persons with Subsidy Application Roles
A person with only subsidy application roles has no account. You can now update these persons, but only with the types social_security_number and birth_name. Other types are rejected with a 422.
Validation of the Social Security Number
social_security_number now has a fixed format. See the API reference for the rule. This applies to POST /persons, to the person updates and to POST /accounts. A value that does not match is rejected with a 400.
Accounts
POST /accounts accepts the optional fields birth_name and social_security_number on the customer object. We store them on the person that we create for the account.
The new types and fields are a preview API and may change without a deprecation period.