---
title: "Batch Update Meeting Records"
method: POST
path: "/api/v3/record/activity/batch/update"
---

# Batch Update Meeting Records

`POST /api/v3/record/activity/batch/update`

## Request body

- object
  - `data` object[] — Add each record's GUID and details below to update them.
    - `id` string, required — Use a meeting record's globally unique identifier (GUID) to update it.
    - `record` object — Set the fields you'd like to update in the specified record.
      - `subject` string, required — The subject of the meeting (Primary).
      - `activitytypecode` integer — The type of activity (Picklist).
      - `description` string — Description of up to 4,000 characters.
      - `location` string — Location
      - `objectid` string — The GUID of the record related to the meeting.
      - `objecttypecode` integer — Object number of the object the related record belongs to. If you set the objectid field, you MUST set this field as well.
      - `ownerid` string — The GUID of the system user who created the record, can also be set manually. Will be used for permissions.
      - `prioritycode` integer — Priority of the meeting (Picklist).
      - `resource` string — The GUID of the resource used for the meeting.
      - `scheduledend` string, date — Date and time the meeting ends in UTC format.
      - `scheduledstart` string, date — Date and time the meeting starts in UTC format.
      - `statuscode` integer — Status (Picklist)

## Response `200`

200

## Other responses

- `400` — 400
- `401` — 401

---

[API](https://skmtc.dev/fireberry/apis/fireberry-api.md) · [All operations](https://skmtc.dev/fireberry/apis/fireberry-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/fireberry/fireberry-api/revisions/ad6720f3920f/schema)