Skip to main content
PUT
One call for a selection, whatever the table: accounts, people or opportunities. Every subject in one request must be the same subject_type, and the tags must come from a group for that subject. The response reports how many records were written. It does not echo each record’s resulting tags: a selection of 100 rows would be a response bigger than the page it repaints.

​
Body

​
object[]
required
1 to 100 records. Each carries subject_type and the key its type uses:
​
string[]
required
Tag ids, from List Tag Groups.
​
string
default:"replace"
add, remove or replace.
​
string
Narrows a replace to one group.
Prefer add over replace across a mixed selection. A bulk replace discards whatever each record already carried, and those rows rarely carried the same thing. The app’s bulk action sends add for exactly this reason.
101 records is an error, not a truncation. The cap is the table’s own page size doubled, which keeps one transaction short enough not to hold row locks across a slow client. Split the selection and send two calls.