Access & visibility
Allow meetings.UpdateMeetingFinding on your API key. Resource read permissions: core:MeetingFinding. Resource write permissions: core:MeetingFinding.
Workspace access by default. Private member data requires approved member delegation through Brigg-Act-As; the key supplies permissions while private ownership and project boundaries remain enforced.
Request fields
Send a JSON object with the following fields. Required fields must be included; omit optional fields you do not need.
idstringRequiredID of a visible core:MeetingFinding record. Use the relevant list operation to discover records. Use the record's top-level id, not a business field or account ID.
dataMeetingFindingOptionalThe fields to set.
MeetingFinding
Finding3 fields
titlestringOptionalShort heading for a finding from the meeting.
bodystringOptionalExplanation or context for the finding.
sourcestringOptionalSource attribution supplied with this finding, when available.
Related meeting1 fields
meeting_idstringOptionalID of a core:Meeting record. Find it with meetings.ListMeetings and use the top-level id. This is not an account ID or a display name.
unsetarray of stringOptionalKeys of data to remove.
Each item: "meeting_id", "title", "body", "source".
expectedobjectOptionalPrior business-field values that must still match before the write. Use fields from this record’s data object, without the data. prefix. Use {"$absent":true} as a value to require an absent field. A mismatch returns 409 conflict. See the conditional example for this resource.
Nested fields
meeting_idstring or objectOptionalCommit only if the previous meeting_id value matches; use $absent to require that this field is missing.
Nested fields
$absent = true
$absenttrueRequiredRequire the field to be missing, rather than present with a null value.
Always true.
titlestring or objectOptionalCommit only if the previous title value matches; use $absent to require that this field is missing.
Nested fields
$absent = true
$absenttrueRequiredRequire the field to be missing, rather than present with a null value.
Always true.
bodystring or objectOptionalCommit only if the previous body value matches; use $absent to require that this field is missing.
Nested fields
$absent = true
$absenttrueRequiredRequire the field to be missing, rather than present with a null value.
Always true.
sourcestring or objectOptionalCommit only if the previous source value matches; use $absent to require that this field is missing.
Nested fields
$absent = true
$absenttrueRequiredRequire the field to be missing, rather than present with a null value.
Always true.
Update without losing changes
Send only the business fields you want to change in data; omitted fields stay unchanged. Use unset to remove an optional field. Setting a field to null is a different action and is allowed only when its schema permits null.
Use expected for a conditional update: supply the values you last read for the fields whose concurrent changes would matter. {"$absent": true} expects a missing field. A conflict means you must read the record again and decide how to reconcile the change. Keep the same idempotency key when retrying the original action; use a new key for a revised action.
Response
Returns 200 OK with a JSON body.
Record metadata sits outside data. Timestamps created_at and updated_at are Unix milliseconds. Optional business fields may be absent; absence does not mean false or zero. A field accepts null only when its type includes null.
itemMeetingFindingRecordRequiredThe requested record, including its metadata and data fields.
MeetingFindingRecord
idstringRequiredStable core:MeetingFinding record ID. Keep this top-level value when reading or referring to this record. Available actions are linked under Next steps; an ID does not imply the resource can be edited.
created_atnumberRequiredTime the record was created, in Unix milliseconds.
updated_atnumberRequiredTime the record most recently changed, in Unix milliseconds. Use with overlapping windows for incremental reads.
created_bystring or nullRequiredAccount that originally created the record, or null for a workspace/system-originated record. This is provenance, not its current owner or a Person record ID.
privatebooleanRequiredTrue for a member-owned private record. An API key needs approved delegation to that owner; false alone does not bypass resource grants or other access rules.
dataMeetingFindingRequiredThe record's fields.
MeetingFinding
Finding3 fields
titlestringRequiredShort heading for a finding from the meeting.
bodystringRequiredExplanation or context for the finding.
sourcestringOptionalSource attribution supplied with this finding, when available.
Related meeting1 fields
meeting_idstringRequiredID of a core:Meeting record. Find it with meetings.ListMeetings and use the top-level id. This is not an account ID or a display name.
Errors & retries
Set BRIGG_REQUEST_ID once for each logical action. The samples send it as Idempotency-Key. Reuse the same value and body on retries, including after a timeout; a missing response does not prove the action failed.
For rate limits, follow the server’s retry guidance and back off. See HTTP errors and safe retries and limits.
| HTTP status | Code | What to do |
|---|---|---|
| 400 | invalid_json |
Send a JSON object with Content-Type: application/json. |
| 400 | invalid_input |
Check the request fields and types. Supply a stable Idempotency-Key containing 1–200 characters. |
| 401 | invalid_key |
The workspace API key is missing, invalid or revoked. |
| 403 | forbidden |
Check the key’s operation and resource grants. If Brigg-Act-As is supplied, the key must be authorized to delegate to that member. |
| 404 | not_found |
The requested operation or resource is not available to this credential. |
| 429 | rate_limited |
Wait for Retry-After before retrying. Reuse the original Idempotency-Key. |
| 409 | conflict |
A supplied expected value no longer matches. Read the record again before deciding whether to retry. |
Next steps
JSON schemas
Use the complete schemas for validation or client generation.
Full request JSON schema
{
"type": "object",
"properties": {
"id": {
"type": "string",
"description": "ID of a visible `core:MeetingFinding` record. Use the relevant list operation to discover records. Use the record's top-level `id`, not a business field or account ID."
},
"data": {
"type": "object",
"properties": {
"meeting_id": {
"type": "string",
"description": "ID of a `core:Meeting` record. Find it with [meetings.ListMeetings](/developers/reference/meetings/ListMeetings) and use the top-level `id`. This is not an account ID or a display name."
},
"title": {
"type": "string",
"description": "Short heading for a finding from the meeting."
},
"body": {
"type": "string",
"description": "Explanation or context for the finding."
},
"source": {
"type": "string",
"description": "Source attribution supplied with this finding, when available."
}
},
"required": [],
"additionalProperties": false,
"description": "The fields to set.",
"title": "MeetingFinding"
},
"unset": {
"type": "array",
"items": {
"type": "string",
"enum": [
"meeting_id",
"title",
"body",
"source"
]
},
"description": "Keys of `data` to remove."
},
"expected": {
"type": "object",
"description": "Prior business-field values that must still match before the write. Use fields from this record’s data object, without the data. prefix. Use {\"$absent\":true} as a value to require an absent field. A mismatch returns 409 conflict. See the conditional example for this resource.",
"additionalProperties": false,
"properties": {
"meeting_id": {
"description": "Commit only if the previous meeting_id value matches; use $absent to require that this field is missing.",
"anyOf": [
{
"type": "string",
"description": "ID of a `core:Meeting` record. Find it with [meetings.ListMeetings](/developers/reference/meetings/ListMeetings) and use the top-level `id`. This is not an account ID or a display name."
},
{
"type": "object",
"properties": {
"$absent": {
"type": "boolean",
"const": true,
"description": "Require the field to be missing, rather than present with a null value."
}
},
"required": [
"$absent"
],
"additionalProperties": false
}
]
},
"title": {
"description": "Commit only if the previous title value matches; use $absent to require that this field is missing.",
"anyOf": [
{
"type": "string",
"description": "Short heading for a finding from the meeting."
},
{
"type": "object",
"properties": {
"$absent": {
"type": "boolean",
"const": true,
"description": "Require the field to be missing, rather than present with a null value."
}
},
"required": [
"$absent"
],
"additionalProperties": false
}
]
},
"body": {
"description": "Commit only if the previous body value matches; use $absent to require that this field is missing.",
"anyOf": [
{
"type": "string",
"description": "Explanation or context for the finding."
},
{
"type": "object",
"properties": {
"$absent": {
"type": "boolean",
"const": true,
"description": "Require the field to be missing, rather than present with a null value."
}
},
"required": [
"$absent"
],
"additionalProperties": false
}
]
},
"source": {
"description": "Commit only if the previous source value matches; use $absent to require that this field is missing.",
"anyOf": [
{
"type": "string",
"description": "Source attribution supplied with this finding, when available."
},
{
"type": "object",
"properties": {
"$absent": {
"type": "boolean",
"const": true,
"description": "Require the field to be missing, rather than present with a null value."
}
},
"required": [
"$absent"
],
"additionalProperties": false
}
]
}
}
}
},
"required": [
"id"
],
"additionalProperties": false,
"examples": [
{
"id": "e_meetingfinding_example",
"data": {
"body": "The pilot starts on 19 October; Alex supplies the source data."
}
}
]
}Full response JSON schema
{
"type": "object",
"properties": {
"item": {
"type": "object",
"properties": {
"id": {
"type": "string",
"description": "Stable core:MeetingFinding record ID. Keep this top-level value when reading or referring to this record. Available actions are linked under Next steps; an ID does not imply the resource can be edited."
},
"created_at": {
"type": "number",
"description": "Time the record was created, in Unix milliseconds."
},
"updated_at": {
"type": "number",
"description": "Time the record most recently changed, in Unix milliseconds. Use with overlapping windows for incremental reads."
},
"created_by": {
"type": [
"string",
"null"
],
"description": "Account that originally created the record, or null for a workspace/system-originated record. This is provenance, not its current owner or a Person record ID."
},
"private": {
"type": "boolean",
"description": "True for a member-owned private record. An API key needs approved delegation to that owner; false alone does not bypass resource grants or other access rules."
},
"data": {
"type": "object",
"properties": {
"meeting_id": {
"type": "string",
"description": "ID of a `core:Meeting` record. Find it with [meetings.ListMeetings](/developers/reference/meetings/ListMeetings) and use the top-level `id`. This is not an account ID or a display name."
},
"title": {
"type": "string",
"description": "Short heading for a finding from the meeting."
},
"body": {
"type": "string",
"description": "Explanation or context for the finding."
},
"source": {
"type": "string",
"description": "Source attribution supplied with this finding, when available."
}
},
"required": [
"meeting_id",
"title",
"body"
],
"additionalProperties": false,
"description": "The record's fields.",
"title": "MeetingFinding"
}
},
"required": [
"id",
"created_at",
"updated_at",
"created_by",
"private",
"data"
],
"additionalProperties": false,
"description": "The requested record, including its metadata and data fields.",
"title": "MeetingFindingRecord"
}
},
"required": [
"item"
],
"additionalProperties": false,
"examples": [
{
"item": {
"id": "e_meetingfinding_example",
"created_at": 1791276900000,
"updated_at": 1791280800000,
"created_by": "a_jamie",
"private": false,
"data": {
"meeting_id": "e_meeting_kickoff",
"title": "Pilot start agreed",
"body": "The pilot starts on 19 October; Alex supplies the source data.",
"source": "Meeting discussion"
}
}
}
]
}