calendars.getInvitationStatus
Check invitation status by UID.
Checks whether an event with a specific iCalendar UID is already filed across any of the mailbox's calendars and returns the user's current RSVP response.
openemail.calendars.getInvitationStatus(
identityId: string,
options: CalendarsGetInvitationStatusOptions,
): ApiPromise<PimInvitationStatus>It calls GET /identities/{identityId}/calendars/invitations: Check invitation status by UID in the API reference.
Example
const pimInvitationStatus = await openemail.calendars.getInvitationStatus(identityId, { uid: '…' })Arguments
| Argument | Type | Description |
|---|---|---|
identityId | string | Identity ULID identifier. The path's {identityId}. |
Options
The last argument, options, takes:
| Option | Type | Sent as | Description |
|---|---|---|---|
uid | string | query uid | Required. iCalendar event UID |
Every call also takes signal, timeout, retry and headers, which say how that one call is sent (call options).
Answer
Awaited, it is the API's JSON, PimInvitationStatus. It is an ApiPromise: .withResponse() gives the same with the Response it came in, for its headers.
Errors
| Status | What it means |
|---|---|
401 | unauthorized: the bearer credential is missing, malformed, expired, or revoked. Carries a WWW-Authenticate: Bearer challenge |
404 | Mailbox not found or not accessible |
503 | temporary_failure: the platform's storage could not answer just now; retry after the Retry-After window. Any operation can answer this. A write that got it may have been applied, so retry it with the same idempotency key where it takes one, or read the state back first (see Transient failures in the API description) |
A failed call rejects with a RequestError: its status, and its code, the API's error. Decide on the code: one status covers several.
Types
It names these types of the API, each on a page of its own: PimInvitationStatus.