Apply the same changes to up to 50 service records in one call. Duplicate ids are counted once. The answer lists which ids were updated and which were not, each with the reason, and is 200 even when every id failed. An id that does not exist is reported as a failed item. changes uses the same field names as the update of one service record. The fields are checked as in that update, but not against each record's template: a field a record's template does not have is left to Ticket Management. A record that is locked by another user, that the caller may not change, whose new status needs a field that is empty, or whose template's form rules refuse the change is reported as a failed item, and the others are still updated. A status or priority change is skipped, with nothing written, for a child ticket, an archived record or a status that does not apply to the record's type. Ticket Management checks the title and the weight once, on the first id, and refuses the whole call (400) when they are not valid. Ticket Management may also fail the whole call (500) after updating some records. A change of the category must send primaryCategory and secondaryCategory, otherwise the request is refused with 400. thirdLevelCategory omitted or null means a two-level category and clears any third level the record had (unlike the single update, which keeps it). Field values are not checked against each record's template; Ticket Management decides per record.
post
https://{account}.sysaidit.com/connect/v1/service-records/bulk-update
