Here it is.
\",\n use_case_id: process.env.NEVARMAIL_USE_CASE_TRANSACTIONAL,\n});\n\nconsole.log(result.id, result.status);\n```\n\n## Tenancy — one key is one org\n\nA NevarMail API key **is** the organization. There is no org id in any request body; the\nserver resolves it from the key and ignores anything you send. Two consequences:\n\n- One key per org. A key cannot be pointed at a second org, and a multi-tenant app that\n sends on behalf of several NevarMail orgs holds several keys.\n- Never accept an org identifier from an end user and pass it through. There is nowhere to\n put it, and the attempt is a sign the integration is modeling tenancy wrong.\n\n## Keys, surfaces, and modes\n\nKeys look like `nvm_api_live_…`, `nvm_api_test_…`, `nvm_mcp_live_…`, `nvm_mcp_test_…`.\n\n- **Surface** (`api` vs `mcp`) — this package speaks REST, so it needs an `api` key. Pass an\n `mcp` key and the constructor throws immediately rather than letting the server answer a\n `403 KEY_TYPE_MISMATCH` at your first send, which reads like an auth bug.\n- **Mode** (`live` vs `test`) — a test key sends only to addresses on the org's test\n allow-list; anything else is a `422 TEST_MODE_RECIPIENT_NOT_ALLOWED`. The mode is a\n property of the key, never a client option: `client.mode` reports what the key is.\n\n```ts\nconst nevarmail = new NevarMail({ apiKey: key });\nif (nevarmail.mode === \"test\") console.warn(\"test key — sends are allow-list only\");\n```\n\n## Errors\n\nEvery failure is a `NevarMailError`:\n\n```ts\nimport { NevarMail, NevarMailError } from \"@bernierllc/nevarmail\";\n\ntry {\n await nevarmail.sendEmail({ to, subject, html });\n} catch (err) {\n if (err instanceof NevarMailError && err.code === \"RECIPIENT_SUPPRESSED\") {\n // Expected: this person opted out. Not an outage.\n return;\n }\n throw err; // everything else is worth waking someone for\n}\n```\n\n| Field | Meaning |\n|---|---|\n| `status` | HTTP status; `0` when the request never reached the API |\n| `code` | Machine-readable code — branch on this, never on `message` |\n| `requestId` | Quote it in support; it matches the API's `x-request-id` |\n| `retryAfter` | Seconds, from `Retry-After` on a 429 |\n| `body` | The parsed response, for codes newer than your installed version |\n\nCodes worth handling explicitly:\n\n| Code | Status | What it means |\n|---|---|---|\n| `RECIPIENT_SUPPRESSED` | 422 | Bounced, complained, or unsubscribed. Do not retry. |\n| `MARKETING_NOT_ENABLED` | 422 | `emailType: \"marketing\"` before marketing is configured (Settings → Marketing, incl. a CAN-SPAM address). |\n| `TEST_MODE_RECIPIENT_NOT_ALLOWED` | 422 | Test key, recipient not on the allow-list. |\n| `CC_BCC_NOT_SUPPORTED_FOR_TEMPLATE` | 400 | Templated mail renders per recipient; send one request each. |\n| `VALIDATION_ERROR` | 400 | The body is wrong. Retrying will not help. |\n| `SCOPE_DENIED` | 403 | The key lacks the scope this route needs. |\n| `KEY_TYPE_MISMATCH` | 403 | An MCP key on a REST route (this client refuses it at construction). |\n| `RATE_LIMITED` | 429 | Retried automatically; surfaced if the budget runs out. |\n| `SCHEDULE_NOT_CANCELLABLE` | 409 | The scheduled send already fired or was already cancelled. |\n| `NETWORK_ERROR` | 0 | No response at all — DNS, TLS, or timeout. |\n\n## Retries\n\nRetried: `429` (honoring `Retry-After`), `5xx`, and network failures — exponential backoff\nwith jitter, two extra attempts by default (`maxRetries`).\n\nNever retried: any other `4xx`. It will fail the same way forever, so retrying turns one bad\nrequest into three. Sends are not idempotent; a retry after a `5xx` may deliver twice.\n\n## Use cases and suppression scope\n\nSuppressions are per project. `checkSuppression(email, useCaseId?, projectId?)` answers for\none project: `projectId`, else the project of `useCaseId`, else the organization's only\nproject. An organization with several projects gets `400 PROJECT_REQUIRED` when neither is\npassed. A bounce or spam complaint on a provider account blocks every project; any other\nsuppression blocks only its own.\n\n`use_case_id` names the message category a send belongs to. It is the difference between\n\"this person unsubscribed from your newsletter\" and \"this person can no longer be emailed\":\n\n- **Name it**, and an opt-out from a *different* category's list does not block the send,\n and a category marked non-suppressable is exempt from opt-outs.\n- **Omit it**, and every active suppression of the project applies — the strict reading.\n\nBounces, spam complaints and manual suppressions block every category regardless. Only a\n`use_case_id` you passed yourself can narrow a block; a default the server resolves cannot.\n\n## Methods\n\n| Method | Route | Scope |\n|---|---|---|\n| `sendEmail` | `POST /api/v1/email/send` | `email:send` |\n| `sendEmailToList` | `POST /api/v1/email/send-to-list` | `email:send` |\n| `scheduleEmail` | `POST /api/v1/email/schedule` | `email:send` |\n| `listScheduledEmails` | `GET /api/v1/email/schedule` | `email:send` |\n| `cancelScheduledEmail` | `DELETE /api/v1/email/schedule/{id}` | `email:send` |\n| `checkSuppression` | `GET /api/v1/suppressions/check` | `org:read` |\n| `getPreferences(email, projectId?)` — one address's lists in one project; `projectId` required when the org has more than one | `GET /api/v1/preferences` | `contacts:read` |\n| `setPreferences(email, { subscribedListIds, unsubscribeAll, projectId? })` — the complete set of lists to stay on | `PUT /api/v1/preferences` | `contacts:write` |\n| `listTemplates` / `createTemplate` / `getTemplate` / `updateTemplate` / `deleteTemplate` | `/api/v1/templates` | `templates:read` / `templates:write` |\n| `renderTemplate` | `POST /api/v1/templates/{id}/render` | `templates:read` |\n| `listLists` / `createList` / `getList` | `/api/v1/lists` | `contacts:read` / `contacts:write` |\n| `addListContacts` | `POST /api/v1/lists/{id}/contacts` | `contacts:write` |\n| `listContacts` / `upsertContacts` / `updateContact` / `deleteContact` | `/api/v1/contacts` | `contacts:read` / `contacts:write` |\n| `listSenders` / `createSender(input)` — `input.projectId?` targets a project when the org has more than one | `/api/v1/senders` | `senders:read` / `senders:write` |\n| `getSender` / `updateSender` / `deleteSender` | `/api/v1/senders/{id}` | `senders:read` / `senders:write` |\n| `importSenders({ projectId? })` — adopts the project's provider-account identities; re-run to pick up provider verification | `POST /api/v1/senders/import` | `senders:write` |\n| `listDomains` / `createDomain(domain, { projectId })` / `getDomain` / `deleteDomain` | `/api/v1/domains` | `domains:read` / `domains:write` |\n| `getDomainDnsRecords` / `verifyDomain` | `/api/v1/domains/{id}/…` | `domains:read` / `domains:write` |\n| `listSuppressions` / `addSuppressions` | `/api/v1/suppressions` | `org:read` / `org:write` |\n| `getInboxDbStatus` | `GET /api/v1/inbox-db/status` | `org:read` |\n| `connectInboxDb({ connectionString, provider? })` / `testInboxDbConnection` | `POST /api/v1/inbox-db/connection` / `…/connection/test` | `org:write` |\n\nApplication-level details worth knowing before you hit them:\n\n- **List methods keep pagination.** `listTemplates` and friends return\n `{ data, pagination: { page, perPage, total } }` — the envelope's pagination is the point of\n calling a list route, so it is not unwrapped away. Single-resource methods return the payload\n directly, same as the send methods.\n- **Updates are `PATCH`, and partial.** Send only the fields you are changing.\n- **`renderTemplate(id, variables)` sends the variables map as the whole body** — not wrapped in\n a `variables` key.\n- **`deleteTemplate` never 404s**: an unknown id resolves `{ deleted: false }` on a 200. Every\n other delete throws on a missing resource.\n- **Lists have no update or delete** — the API exposes none; the SDK does not invent them.\n- **Suppression scope is cross-field**: `scope: \"use_case\"` requires `use_case_id`, and\n `use_case_id` with `scope: \"account\"` is a `400`. `projectId` names the project the rows land\n in; omitted, they land in the use case's project, else in every project the key's owner can open.\n- **Managed accounts cannot delete domains** — `deleteDomain` throws `403 MANAGED_ACCOUNT`.\n- **The inbox-db connection string is sent once and never echoed.** `connectInboxDb` stores it encrypted; `InboxDbStatus` omits it. `schemaName` is the Postgres schema NevarMail owns in your database.\n\nAnything still not covered — analytics, campaigns, webhook endpoints — goes through\n`request()` (or `requestPaginated()` for list routes), which applies the same auth, envelope\nunwrapping, throwing, and retries:\n\n```ts\nconst summary = await nevarmail.request