Skip to main content
POST
Reveal Sensitive Entity Field Value

Authentication and permissions

Token requirements: User-based token (OAuth) or Organization-scoped API key or Team-scoped API key. Send a bearer access token for one of these identities. The permissions and resource restrictions below also apply.
Permissions joined by + are all required; or separates alternatives. Full-access keys still cannot call endpoints marked unsupported. Team keys must allow every team checked by the request. OAuth access depends on the user’s roles and resource access.
  • Read a record in a team’s database, or in a database shared with one of your teams: The permission is checked on the record’s owning team, or on a team the record’s database is shared with (“Can read” or “Can write”). A record in a database not shared with one of your teams is refused. Schema and row-access rules still apply.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

entity_id
string
required

The ID of the entity. Readable in its owning team or through a team its database is shared with.

Body

application/json
fieldId
string
required

The field's ID as returned in field_values[].field_id by entity reads. Set exactly one of field_id or field_key.

includeHistory
boolean

Also return the field's value history on this entity, most recent first. Recorded on the audit event.

Response

200 - application/json

Success

data
data · object

The current value. sensitive is false and value is set when the entity stores one.

history
EntityFieldValue · object[]

Present only when include_history was requested.