What both personal-attribute routes answer: the entity in its canonical spelling, and every attribute it carries for the requesting profile. An unset attribute is an absent key, never a null.
API reference sections
Schema
PersonalAttributesResponse
Type object
Shape
| Field | Type | Description |
|---|---|---|
| entityrequired | string | |
| attributesrequired | map of string to PersonalAttributeValue |
{
"entity": "string",
"attributes": {
"key": {
"text": "string",
"type": "text"
}
}
}The contract has no example values, so example bodies are generated from each schema: every field is shown with a placeholder of its type.
Used by
GET
One profile's personal attributes for one entity, named by ?entity=<kind>:<workspace>:<document>:<node>/v1/profiles/{id}/personal-attributesPUT
Set one personal attribute on one entity, or clear it with a null value/v1/profiles/{id}/personal-attributes
Generated from contract version 1. Last updated .
