/api/v1/object/data/{objectSlug}/bulk-assignSet the assignees of up to 500 records.
Set the assignees of up to 500 records.
assignees is the full assignee list for every record in slugs: it
replaces the current list, and [] removes everyone. A record keeps its
owner when the owner is still in the list; otherwise the first slug
becomes the owner. admin_slug is the older single-owner form, equal to
assignees: [admin_slug]. Send one of the two; sending neither removes
all assignees. Slugs that match no record are skipped; updatedCount
says how many records were found and assigned. A record takes at most 20
assignees.
Scope: assign.<object slug>, for example assign.contacts.
Errors:
400— bothadmin_slugandassigneesare sent, or no active object has that slug.403— the credential may not edit one of the records.422— more than 20 assignees (code: TOO_MANY_ASSIGNEES), an assignee is not a user of this workspace (code: INVALID_ASSIGNEE), or the body is invalid, for example more than 500 slugs.
Request:
{
"slugs": ["9f2c4b7a1e03", "c83e1a5f2d97"],
"assignees": ["a3f1b2c8e9d7", "e6d2b9f41c08"]
}
Response 200:
{
"status": 200,
"message": "Bulk assign completed",
"data": { "updatedCount": 2 }
}
Send request
Use the documented inputs to call this endpoint directly.
Parameters
Values are applied to the request and the example on the right.
Request body
application/jsonrequiredSingle-owner form kept for existing clients: equivalent to
assignees: [admin_slug]. Mutually exclusive with {@link assignees}.
The desired FULL assignee set for every selected record (set-replace, same
semantics as PATCH …/:recordSlug/assignees). First slug becomes the
primary owner; [] unassigns everyone.
Responses
Successful response
{
"message": "string",
"data": "string"
}Bad request
{
"status": 1,
"message": "string",
"code": "string",
"data": {}
}The HTTP status code of the response.
What went wrong. Several validation messages are joined with ", ".
A stable, machine-readable reason. Only some errors set it.
Extra detail about the error. Only some errors set it.
Unauthorized
{
"status": 1,
"message": "string",
"code": "string",
"data": {}
}The HTTP status code of the response.
What went wrong. Several validation messages are joined with ", ".
A stable, machine-readable reason. Only some errors set it.
Extra detail about the error. Only some errors set it.
Internal server error
{
"status": 1,
"message": "string",
"code": "string",
"data": {}
}The HTTP status code of the response.
What went wrong. Several validation messages are joined with ", ".
A stable, machine-readable reason. Only some errors set it.
Extra detail about the error. Only some errors set it.
Powered by heyo-docs