Create meeting finding — Brigg developers

Access & visibility

Allow meetings.CreateMeetingFinding 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.

Set up authentication · Choose permissions

Request fields

Send a JSON object with the following fields. Required fields must be included; omit optional fields you do not need.

dataMeetingFindingRequired

The record's fields.

MeetingFinding

Finding3 fields

titlestringRequired

Short heading for a finding from the meeting.

bodystringRequired

Explanation or context for the finding.

sourcestringOptional

Source attribution supplied with this finding, when available.

Related meeting1 fields

meeting_idstringRequired

ID 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.

privatebooleanOptional

Defaults to false: the record is shared with the workspace. True assigns private ownership to the approved acting member and requires member delegation. This is independent of created_by provenance.

Choose ownership deliberately

Omitting private, or setting it to false, creates a workspace-shared record. Set private: true to create a record owned by the approved acting member. Private records require member delegation; a workspace-only credential cannot own a personal record. The credential’s exact resource grants authorize the write; private ownership and project membership remain enforced.

A create is a new record, not an upsert. Reuse the same idempotency key only for retries of that logical creation. For recurring synchronization, use the resource’s upsert operation when available: it matches a permanent external reference. Otherwise keep the returned record ID and use the corresponding update operation for subsequent changes.

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.

itemMeetingFindingRecordRequired

The requested record, including its metadata and data fields.

MeetingFindingRecord

idstringRequired

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_atnumberRequired

Time the record was created, in Unix milliseconds.

updated_atnumberRequired

Time the record most recently changed, in Unix milliseconds. Use with overlapping windows for incremental reads.

created_bystring or nullRequired

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.

privatebooleanRequired

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.

dataMeetingFindingRequired

The record's fields.

MeetingFinding

Finding3 fields

titlestringRequired

Short heading for a finding from the meeting.

bodystringRequired

Explanation or context for the finding.

sourcestringOptional

Source attribution supplied with this finding, when available.

Related meeting1 fields

meeting_idstringRequired

ID 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.

Next steps

Download OpenAPI · Versioning & retirement

JSON schemas

Use the complete schemas for validation or client generation.

Full request JSON schema

{
  "type": "object",
  "properties": {
    "data": {
      "type": "object",
      "properties": {
        "meeting_id": {
          "type": "string",
          "description": "ID of a `core:Meeting` record. Find it with [meetings.ListMeetings](/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"
    },
    "private": {
      "type": "boolean",
      "description": "Defaults to false: the record is shared with the workspace. True assigns private ownership to the approved acting member and requires member delegation. This is independent of created_by provenance."
    }
  },
  "required": [
    "data"
  ],
  "additionalProperties": false,
  "examples": [
    {
      "data": {
        "meeting_id": "e_meeting_kickoff",
        "title": "Pilot start agreed",
        "body": "The pilot starts on 19 October.",
        "source": "Meeting discussion"
      }
    }
  ]
}

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](/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.",
          "source": "Meeting discussion"
        }
      }
    }
  ]
}

Try the request

Use your API key in a server environment.

Act as a memberRequires administrator-approved delegation.

Fictional values. Replace IDs and business details with values from your workspace.

Request

cURL

curl 'https://api.brigg.app/v1/operations/meetings.CreateMeetingFinding' \
  -H "Authorization: Bearer $BRIGG_API_KEY" \
  -H 'Content-Type: application/json' \
  -H "Idempotency-Key: $BRIGG_REQUEST_ID" \
  --data-raw '{
  "data": {
    "meeting_id": "e_meeting_kickoff",
    "title": "Pilot start agreed",
    "body": "The pilot starts on 19 October.",
    "source": "Meeting discussion"
  }
}'

TypeScript

const requestId = process.env.BRIGG_REQUEST_ID;
if (!requestId) throw new Error("Set BRIGG_REQUEST_ID once per action and reuse it on retries.");

const response = await fetch("https://api.brigg.app/v1/operations/meetings.CreateMeetingFinding", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.BRIGG_API_KEY}`,
    "Content-Type": "application/json",
    "Idempotency-Key": requestId, // Create once per action; reuse on retries.
  },
  body: JSON.stringify({
    "data": {
      "meeting_id": "e_meeting_kickoff",
      "title": "Pilot start agreed",
      "body": "The pilot starts on 19 October.",
      "source": "Meeting discussion"
    }
  }),
});
const result = await response.json();
if (!response.ok) throw new Error(`${response.status}: ${result.error} — ${result.message}`);
console.log(result);

Python

import json
import os
from urllib.request import Request, urlopen
from urllib.error import HTTPError

request_id = os.environ["BRIGG_REQUEST_ID"]  # Reuse for retries of this action.
payload = {
  "data": {
    "meeting_id": "e_meeting_kickoff",
    "title": "Pilot start agreed",
    "body": "The pilot starts on 19 October.",
    "source": "Meeting discussion"
  }
}
request = Request(
    "https://api.brigg.app/v1/operations/meetings.CreateMeetingFinding",
    data=json.dumps(payload).encode("utf-8"),
    headers={
        "Authorization": f"Bearer {os.environ['BRIGG_API_KEY']}",
        "Content-Type": "application/json",
        "Idempotency-Key": request_id,  # Create once per action; reuse on retries.
    },
    method="POST",
)
try:
    with urlopen(request) as response:
        print(json.load(response))
except HTTPError as error:
    print(error.code, json.load(error))
    raise

cURL

curl 'https://api.brigg.app/v1/operations/meetings.CreateMeetingFinding' \
  -H "Authorization: Bearer $BRIGG_API_KEY" \
  -H 'Content-Type: application/json' \
  -H "Brigg-Act-As: $BRIGG_ACT_AS" \
  -H "Idempotency-Key: $BRIGG_REQUEST_ID" \
  --data-raw '{
  "data": {
    "meeting_id": "e_meeting_kickoff",
    "title": "Pilot start agreed",
    "body": "The pilot starts on 19 October.",
    "source": "Meeting discussion"
  }
}'

TypeScript

const actAs = process.env.BRIGG_ACT_AS;
if (!actAs) throw new Error("Set BRIGG_ACT_AS to an approved member account ID.");

const requestId = process.env.BRIGG_REQUEST_ID;
if (!requestId) throw new Error("Set BRIGG_REQUEST_ID once per action and reuse it on retries.");

const response = await fetch("https://api.brigg.app/v1/operations/meetings.CreateMeetingFinding", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.BRIGG_API_KEY}`,
    "Content-Type": "application/json",
    "Brigg-Act-As": actAs,
    "Idempotency-Key": requestId, // Create once per action; reuse on retries.
  },
  body: JSON.stringify({
    "data": {
      "meeting_id": "e_meeting_kickoff",
      "title": "Pilot start agreed",
      "body": "The pilot starts on 19 October.",
      "source": "Meeting discussion"
    }
  }),
});
const result = await response.json();
if (!response.ok) throw new Error(`${response.status}: ${result.error} — ${result.message}`);
console.log(result);

Python

import json
import os
from urllib.request import Request, urlopen
from urllib.error import HTTPError

request_id = os.environ["BRIGG_REQUEST_ID"]  # Reuse for retries of this action.
payload = {
  "data": {
    "meeting_id": "e_meeting_kickoff",
    "title": "Pilot start agreed",
    "body": "The pilot starts on 19 October.",
    "source": "Meeting discussion"
  }
}
request = Request(
    "https://api.brigg.app/v1/operations/meetings.CreateMeetingFinding",
    data=json.dumps(payload).encode("utf-8"),
    headers={
        "Authorization": f"Bearer {os.environ['BRIGG_API_KEY']}",
        "Content-Type": "application/json",
        "Brigg-Act-As": os.environ["BRIGG_ACT_AS"],
        "Idempotency-Key": request_id,  # Create once per action; reuse on retries.
    },
    method="POST",
)
try:
    with urlopen(request) as response:
        print(json.load(response))
except HTTPError as error:
    print(error.code, json.load(error))
    raise

200 OK Response example

{
  "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.",
      "source": "Meeting discussion"
    }
  }
}

Illustrative values, not a live response.