Skip to main content
PUT
Update Entities

Authentication and permissions

Token requirements: User-based token (OAuth) or Organization-scoped API key or Workspace-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. Workspace keys must allow every workspace checked by the request. OAuth access depends on the user’s roles and resource access.
  • Change a record in a workspace’s database, or in a database shared with one of your workspaces: The permission is checked on the record’s owning workspace, or on a workspace the record’s database is shared with; Read alone admits no changes. A record in a database not shared with one of your workspaces is refused. Update requires Update access; archive and unarchive require Delete access. Database, table, field and record conditions still apply.

Authorizations

Authorization
string
header
required

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

Body

application/json
entityIds
string[]
required

Up to 100 record IDs from one table. Duplicate IDs are updated once.

fieldValues
EntityFieldValueInput · object[]
required

Set these values on every selected record; omitted fields are unchanged.

Response

200 - application/json

Success

data
Entity · object[]
pendingChanges
EntityPendingChange · object[]
failures
UpdateEntitiesFailure · object[]