Calendar Event Confirmation Statuses

Reference for the calendar_event_confirmation_statuses resource. Requests follow the conventions in Requests and Responses; fields you receive and may write are filtered by your user's permissions, so responses can contain a subset of the fields below.

Operations

Not available as a standard REST operation for this resource: create, update, delete — such requests return 402 feature_not_enabled or 403 permission_denied.

How it works

calendar_event_confirmation_statuses is the read-only catalog of appointment confirmation statuses — the valid confirmation_status_id values when recording a confirmation. The standard set is Not Confirmed, Accepted, and Cancelled.

Read-only fixed seeds. Readable by anyone with a scheduler view permission.

curl "https://portal.securitytrax.com/acme/user/v4/calendar_event_confirmation_statuses" \
  -H "Authorization: Bearer stx_acme_..."

Filter by name (matches anywhere); sort by id or name; GET /{id} fetches one.

Fields

Fields are grouped by the permission that gates them. A group you may not view is absent from responses; a group you may not write is rejected with 422 when sent in a write.

Confirmation Status

View: any of: special access rules; special access rules; special access rules; special access rules.

Pagination

The list endpoint uses client-controlled offset pagination: ?page= (1-based) and ?per_page= (default 25, max 100). The response mirrors meta.pagination (page, per_page, total, last_page) and sends an RFC5988 Link header; follow rel="next" to walk pages. See Pagination.

Filters

The list endpoint accepts these query-param filters: name. An unsupported filter parameter returns 422. See Filtering collections for matching semantics.

Sorting

GET .../calendar_event_confirmation_statuses?sort= orders the list by: id, name. Prefix a field with - for descending; comma-separate for tie-breakers. An unsupported field returns 422. See Sorting collections.

Related

• Requests and Responses — envelope, errors, pagination, and rate limits.
• Authentication — tokens and the Authorization header.