Create Personal Data Field
POST /obp/v7.0.0/my/personal-data-fields
OBPv6.0.0-createPersonalDataField No role required UserUser-AttributeAttribute
Create a Personal Data Field for the currently authenticated user.
Personal Data Fields (IsPersonal=true) are managed by the user themselves and do not require special roles. This data is not available in ABAC rules for privacy reasons.
For non-personal attributes that can be used in ABAC rules, see the /users/USER_ID/attributes endpoints.
The type field must be one of "STRING", "INTEGER", "DOUBLE", "DECIMAL", "BOOLEAN" and "DATE_WITH_DAY". Use "DECIMAL" rather than "DOUBLE" for rates, prices and amounts, because it holds the value exactly; "BOOLEAN" values are "true" or "false".
Each Personal Data Field is identified by its own USER_ATTRIBUTE_ID. The "name" is not a unique key: this endpoint always creates a new field, so the same "name" can occur on multiple fields for the same user (e.g. two "phone_number" fields). To change the value of an existing field, use PUT /my/personal-data-fields/USER_ATTRIBUTE_ID rather than POSTing again. To list a user's fields and their USER_ATTRIBUTE_IDs, use GET /my/personal-data-fields.
User Authentication is Required. The User must be logged in. The Application must also be authenticated.
JSON response body fields (6)
Example request body
{
"name": "favorite_color",
"type": "STRING",
"value": "blue"
}Example success response
{
"user_attribute_id": "7uy8a7e4-6d02-40e3-a129-0b2bf89de8uh",
"name": "BATTERY_LEVEL",
"type": "STRING",
"value": "90",
"is_personal": false,
"insert_date": "2026-10-21T01:45:41Z"
}Possible errors (3)
- OBP-20001: User not logged in. Authentication is required!
- OBP-10001: Incorrect json format.
- OBP-50000: Unknown Error.