Skip to Content

Revoke calendar access.

Revokes a mailbox's access grant to a calendar collection.

openemail.calendars.revokeAccess(
  identityId: string,
  calendarId: string,
  shareeIdentityId: string,
  options?: CallOptions,
): ApiPromise<CalendarsRevokeAccessResult>

It calls DELETE /identities/{identityId}/calendars/{calendarId}/shares/{shareeIdentityId}: Revoke calendar access in the API reference.

Example

const result = await openemail.calendars.revokeAccess(identityId, calendarId, shareeIdentityId)

Arguments

ArgumentTypeDescription
identityIdstringMailbox identity ULID. The path's {identityId}.
calendarIdstringCollection ULID or its name slug. The path's {calendarId}.
shareeIdentityIdstringThe grantee's mailbox identity ULID. The path's {shareeIdentityId}.

Options

It takes no options of its own. 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, CalendarsRevokeAccessResult. It is an ApiPromise: .withResponse() gives the same with the Response it came in, for its headers.

Errors

StatusWhat it means
401unauthorized: the bearer credential is missing, malformed, expired, or revoked. Carries a WWW-Authenticate: Bearer challenge
404No such grant, collection, or mailbox
503temporary_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

CalendarsRevokeAccessResult

/** What `calendars.revokeAccess` answers. */
type CalendarsRevokeAccessResult = {
  deleted: boolean
}