Skip to content

API reference

Cancel calendar event

meetings.CancelCalendarEventWriteAPI key

Delete a Brigg-owned calendar event and optionally send cancellation notices to attendees. Set send_cancel to send those notices. This does not cancel an event in a connected Google or Microsoft calendar.

POST/v1/operations/meetings.CancelCalendarEvent
On this page

Access & visibility

Allow meetings.CancelCalendarEvent on your API key. Resource write permissions: core:CalendarEvent.

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.

idstringRequired

The core:CalendarEvent entry id.

At least 1 character.

send_cancelbooleanOptional

Mail an iCal CANCEL to every attendee.

messagestringOptional

Message included with the calendar invitation update or cancellation.

Response

Returns 200 OK with a JSON body.

idstringRequired

Unique identifier. Use the value returned by a create or list operation.

uidstringRequired

Calendar invitation UID, distinct from the Brigg record ID.

sendobjectOptional

Present when a mail-out was asked for.

Nested fields
message_idsmap of stringRequired

Recipient email address to delivery message ID.

skippedarray of stringRequired

Attendee account ids with no email address.

rate_limitedbooleanOptional

The org's invite quota was hit — the event write landed, no mail went out.

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": {
    "id": {
      "type": "string",
      "minLength": 1,
      "description": "The core:CalendarEvent entry id."
    },
    "send_cancel": {
      "type": "boolean",
      "description": "Mail an iCal CANCEL to every attendee."
    },
    "message": {
      "type": "string",
      "description": "Message included with the calendar invitation update or cancellation."
    }
  },
  "required": [
    "id"
  ],
  "additionalProperties": false,
  "examples": [
    {
      "id": "e_example"
    }
  ]
}
Full response JSON schema
{
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "description": "Unique identifier. Use the value returned by a create or list operation."
    },
    "uid": {
      "type": "string",
      "description": "Calendar invitation UID, distinct from the Brigg record ID."
    },
    "send": {
      "type": "object",
      "description": "Present when a mail-out was asked for.",
      "properties": {
        "message_ids": {
          "description": "Recipient email address to delivery message ID.",
          "type": "object",
          "additionalProperties": {
            "type": "string"
          }
        },
        "skipped": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Attendee account ids with no email address."
        },
        "rate_limited": {
          "type": "boolean",
          "description": "The org's invite quota was hit — the event write landed, no mail went out."
        }
      },
      "required": [
        "message_ids",
        "skipped"
      ],
      "additionalProperties": false
    }
  },
  "required": [
    "id",
    "uid"
  ],
  "additionalProperties": false,
  "examples": [
    {
      "id": "e_example",
      "uid": "kickoff@example.com"
    }
  ]
}

Search by operation name or what you want to build.

Use arrow keys to browse. Enter opens a result.