sieve.check
Validate a Sieve filter script without saving.
Dry-run validates Sieve script syntax and returns line and column numbers on error.
openemail.sieve.check(
mailboxId: string,
body: SieveCheckBody,
options?: CallOptions,
): ApiPromise<SieveCheckResult>It calls POST /mailboxes/{mailboxId}/sieve/check: Validate a Sieve filter script without saving in the API reference.
Example
const result = await openemail.sieve.check(mailboxId, { script: '…' })Arguments
| Argument | Type | Description |
|---|---|---|
mailboxId | string | Mailbox ULID identifier. The path's {mailboxId}. |
body | SieveCheckBody | The request's body. |
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, SieveCheckResult. It is an ApiPromise: .withResponse() gives the same with the Response it came in, for its headers.
Errors
| Status | What it means |
|---|---|
400 | validation_failed — malformed body |
401 | unauthorized: the bearer credential is missing, malformed, expired, or revoked. Carries a WWW-Authenticate: Bearer challenge |
404 | Mailbox not found or not accessible to this principal |
413 | too_large: JSON request body exceeds 1 MiB or 500,000 values (object keys included), checked before parsing |
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
SieveCheckBody
/** The body of `sieve.check`. */
type SieveCheckBody = {
/** Sieve script source code */
script: string
}It names these types of the API, each on a page of its own: SieveCheckResult.