verifiedRecipients.getConfirmPage
Verified recipient confirmation link (the page).
Public. Renders the page a verified recipient's confirmation link opens: the address, and a Confirm button whose form POSTs to the same URL. A GET never confirms anything, because link scanners prefetch URLs. No bearer credential: the signed token in the path IS the credential, and its holder is the owner of an outside address.
openemail.verifiedRecipients.getConfirmPage(
token: string,
options?: CallOptions,
): ApiPromise<string>It calls GET /recipients/confirm/{token}: Verified recipient confirmation link (the page) in the API reference. The operation is public: the client sends it without its credential.
Example
const text = await openemail.verifiedRecipients.getConfirmPage(token)Arguments
| Argument | Type | Description |
|---|---|---|
token | string | Signed confirmation-link token. The path's {token}. |
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 text the API answers, a string. It is an ApiPromise: .withResponse() gives the same with the Response it came in, for its headers.
Errors
| Status | What it means |
|---|---|
403 | A page saying the link is not valid, has expired (links work for seven days), or no longer works (its address was removed, or a newer link replaced it) |
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.