Set meeting summary emails — Brigg developers

Access & visibility

Allow meetings.SetMeetingSummaryEmails on your API key.

Acting member required. Send Brigg-Act-As with an approved member account ID. The key supplies permissions; the member selects whose data is used.

The selected member must be active and approved by the credential. This selects whose private data is used; the credential supplies permissions. Private ownership and project boundaries still apply.

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.

scopestringRequired

Automatic attendee-email audience for meetings hosted by the acting member: all includes external attendees, external means only people outside the workspace, internal means workspace colleagues only, and off disables attendee emails. This is a delivery preference, not meeting visibility.

Allowed: "all", "external", "internal", "off".

Change the host's future delivery preference

With member delegation, this updates the approved acting member's own preference, not a workspace-wide default. Automatic delivery reads the meeting host's preference when a summary is generated. This call saves a setting; it does not send old summaries, recall delivered messages or confirm any later delivery.

The default attendee setting is off when no preference is stored. The host's own summary email has a separate setting: off here does not disable that personal copy. Review current preferences in Brigg Settings; this operation returns the newly saved value rather than the previous one.

Response

Returns 200 OK with a JSON body.

scopestringRequired

The saved attendee-email preference, matching the requested scope. It does not report a message send or delivery outcome.

Allowed: "all", "external", "internal", "off".

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. Supply Brigg-Act-As with a member authorized by the key’s delegation grant. The selected member must be active and approved by the credential. This selects whose private data is used; the credential supplies permissions. Private ownership and project boundaries still apply.
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": {
    "scope": {
      "type": "string",
      "enum": [
        "all",
        "external",
        "internal",
        "off"
      ],
      "description": "Automatic attendee-email audience for meetings hosted by the acting member: all includes external attendees, external means only people outside the workspace, internal means workspace colleagues only, and off disables attendee emails. This is a delivery preference, not meeting visibility."
    }
  },
  "required": [
    "scope"
  ],
  "additionalProperties": false,
  "examples": [
    {
      "scope": "internal"
    }
  ]
}

Full response JSON schema

{
  "type": "object",
  "properties": {
    "scope": {
      "type": "string",
      "enum": [
        "all",
        "external",
        "internal",
        "off"
      ],
      "description": "The saved attendee-email preference, matching the requested scope. It does not report a message send or delivery outcome."
    }
  },
  "required": [
    "scope"
  ],
  "additionalProperties": false,
  "examples": [
    {
      "scope": "internal"
    }
  ]
}

Try the request

Use your API key in a server environment.

Example scenario

Requires BRIGG_ACT_AS: an approved member account ID.

External attendees will not receive automatic attendee emails under this setting.

Request

cURL

curl 'https://api.brigg.app/v1/operations/meetings.SetMeetingSummaryEmails' \
  -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 '{
  "scope": "internal"
}'

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.SetMeetingSummaryEmails", {
  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({
    "scope": "internal"
  }),
});
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 = {
  "scope": "internal"
}
request = Request(
    "https://api.brigg.app/v1/operations/meetings.SetMeetingSummaryEmails",
    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

{
  "scope": "internal"
}

Illustrative values, not a live response.

The host's own summary email remains controlled separately.