API Explorer 936 endpoints

Update Personal Data Field

PUT /obp/v7.0.0/my/personal-data-fields/USER_ATTRIBUTE_ID

OBPv6.0.0-updatePersonalDataField No role required UserUser-AttributeAttribute

Update a single Personal Data Field by USER_ATTRIBUTE_ID for the currently authenticated user.

USER_ATTRIBUTE_ID identifies the exact field to update; this updates that one field in place and never creates a new one. The body's "name", "type" and "value" all replace the existing field's values, so a field can be renamed by changing "name". Returns 404 if no field with that USER_ATTRIBUTE_ID belongs to the user. 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".

User Authentication is Required. The User must be logged in. The Application must also be authenticated.

URL Parameters:

USER_ATTRIBUTE_ID: 7uy8a7e4-6d02-40e3-a129-0b2bf89de8uh

JSON response body fields (6)
insert_date
2020-01-27
is_personal
is_personal
name
ACCOUNT_MANAGEMENT_FEE
type
user_attribute_id
7uy8a7e4-6d02-40e3-a129-0b2bf89de8uh
value
5987953
Example request body
{
  "name": "favorite_color",
  "type": "STRING",
  "value": "green"
}
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 (4)
  • OBP-20001: User not logged in. Authentication is required!
  • OBP-20081: User Attribute not found by USER_ATTRIBUTE_ID.
  • OBP-10001: Incorrect json format.
  • OBP-50000: Unknown Error.
Implemented by OBPv6.0.0 updatePersonalDataField Originally /obp/v6.0.0/my/personal-data-fields/USER_ATTRIBUTE_ID