sequenzy 2.0.0 → 2.1.4

package/dist/esm/api/resources/transactional/client/Client.d.ts

@@ -21,7 +21,9 @@ export declare class TransactionalClient {
      *
      * @throws {@link Sequenzy.BadRequestError}
      * @throws {@link Sequenzy.UnauthorizedError}
+     * @throws {@link Sequenzy.ForbiddenError}
      * @throws {@link Sequenzy.ConflictError}
+     * @throws {@link Sequenzy.UnprocessableEntityError}
      * @throws {@link Sequenzy.InternalServerError}
      * @throws {@link errors.SequenzyError}
      * @throws {@link errors.SequenzyTimeoutError}
@@ -38,7 +40,7 @@ export declare class TransactionalClient {
      *
      * Already-sent deliveries are untouched: send history, stats, and stored HTML live on the deliveries themselves.
      *
-     * The email content is kept as a reusable template and returned as `deleted.emailId`; pass that to `DELETE /api/v1/templates/{templateId}` to remove the content too. To stop sends without losing the template, update it with `enabled: false` instead.
+     * The email content is kept as a reusable template and returned as `deleted.emailId`; pass that to `DELETE /api/v1/templates/{templateId}` to remove the content too. Code-managed emails (`managedBy: code`) are the exception: their content snapshot is deleted with them, so the returned `emailId` no longer exists. To stop sends without losing the template, update it with `enabled: false` instead.
      *
      * Requires an API key with the `transactional:delete` scope.
      *
@@ -67,6 +69,7 @@ export declare class TransactionalClient {
      * @param {TransactionalClient.RequestOptions} requestOptions - Request-specific configuration.
      *
      * @throws {@link Sequenzy.UnauthorizedError}
+     * @throws {@link Sequenzy.ForbiddenError}
      * @throws {@link Sequenzy.NotFoundError}
      * @throws {@link Sequenzy.InternalServerError}
      * @throws {@link Sequenzy.ServiceUnavailableError}
@@ -86,7 +89,10 @@ export declare class TransactionalClient {
      * @param {Sequenzy.ListTransactionalRequest} request
      * @param {TransactionalClient.RequestOptions} requestOptions - Request-specific configuration.
      *
+     * @throws {@link Sequenzy.BadRequestError}
      * @throws {@link Sequenzy.UnauthorizedError}
+     * @throws {@link Sequenzy.ForbiddenError}
+     * @throws {@link Sequenzy.UnprocessableEntityError}
      * @throws {@link Sequenzy.InternalServerError}
      * @throws {@link Sequenzy.ServiceUnavailableError}
      * @throws {@link errors.SequenzyError}
@@ -102,12 +108,21 @@ export declare class TransactionalClient {
      *
      * For callers that may retry, send a stable `Idempotency-Key` header. The same key and request returns the original `emailSendId` for 14 days without another delivery. Reusing a key with different request content returns 409.
      *
+     * Repeated identical transactional content reaching many distinct recipients can trigger a junk/list-testing review. Sending continues while review is pending or unavailable. A substantiated verdict can reject later matching deliveries before sending; these become terminal `failed` sends with an `errorMessage` beginning `Transactional content rejected:`. Read GET /email-sends/{emailSendId} for the final outcome. Failed deliveries are not held or replayed automatically, and replaying the same Idempotency-Key returns the original acceptance response. Dashboard retries of rejected deliveries also fail without sending, even after the decision expires. Correct the content or contact support before deliberately submitting a new logical send. This check does not pause the company or ban the account.
+     *
      * You can either:
      * - Provide a canonical `slug` (or compatibility alias `templateId`) to use a saved template
      * - Provide `subject` and canonical `body` (or compatibility alias `html`) to send custom content directly
      *
      * If both a canonical field and its alias are provided, `slug` must match `templateId` and `body` must match `html`.
      *
+     * **Tracking direct-content sends:**
+     * - Set `trackAs` on a direct-content send (for example `weekly-report`) to count it under one code-managed transactional email. The first send with a new value creates it with `managedBy: code`; later sends with the same value link to it. The value may use up to 255 ASCII letters, digits, spaces and `. _ - : /`, and is normalized like a slug (`Weekly Report` and `weekly-report` are the same email). Other values, including empty ones, return 400 `INVALID_TRACK_AS`.
+     * - Opens, clicks, bounces and the other transactional stats then aggregate on that email, and it appears in `GET /transactional` next to your saved templates. Its subject, preview text and HTML are a snapshot of a recent send, refreshed at most every 10 minutes and stored before variable substitution.
+     * - Disabling the code-managed email makes further sends with that `trackAs` fail with 400 `TRACKED_EMAIL_DISABLED` until you enable it again. Deleting it lets the next send recreate it with fresh stats.
+     * - `trackAs` cannot be combined with `slug`/`templateId`, cannot reuse the slug of a template managed in the dashboard, and a company can have at most 100 code-managed emails. Use a stable name for an email type, never per-recipient values. Code-managed emails cannot be sent by `slug`.
+     * - The email is created after the send passes request validation, so an invalid send does not create it. A send that fails later, for example on an `Idempotency-Key` conflict, can still leave the newly created email with no sends.
+     *
      * **Recipients:**
      * - `to` can be a single email or an array of up to 50 emails
      * - Duplicate emails are automatically deduplicated
@@ -115,16 +130,18 @@ export declare class TransactionalClient {
      *
      * **Attachments:**
      * - Attachments can be provided as Base64-encoded content or URLs
-     * - Maximum 10 attachments and 7MB total per email
+     * - Maximum 10 attachments and 15MB total per email
      * - Any file type supported (PDFs, images, documents, etc.)
      * - Set `contentId` on an attachment to embed it as an inline image referenced from the HTML as `<img src="cid:VALUE">`
      *
      * A successful response means the email was accepted for background processing. Transactional emails are not blocked by subscriber unsubscribe or double opt-in status. If a recipient is suppressed because of a hard bounce or spam complaint, the worker records the send as `suppressed` instead of delivering it.
      *
      * Optionally set `from` (domain must be verified) and `replyTo` addresses. When reply tracking is enabled, Sequenzy uses a unique trackable `Reply-To` header and treats the resolved reply destination as the forwarding destination for captured replies.
-     * When `replyTo` is omitted, direct-content sends inherit the company's default reply profile and saved-template sends prefer the template reply profile before the company default. Both fall back to the first company reply profile. The resolved destination is retained whether or not reply tracking is enabled; it is sent as the Reply-To header only when reply tracking is disabled.
+     * Without a reply identity override, saved-template sends prefer the template reply profile. Otherwise sends prefer the effective sending domain's default reply profile, then the company default, then the first company reply profile. The resolved destination is retained whether or not reply tracking is enabled; it is sent as the Reply-To header only when reply tracking is disabled.
      * Variables can be passed to customize the email content. Nested objects and arrays are supported for repeat blocks, such as `items`. `{{viewInBrowserUrl}}` is generated automatically for a hosted copy link. For a single recipient, Sequenzy matches an existing subscriber by `subscriberExternalId` or email and backfills stored first and last names when the corresponding request variables are omitted; explicit variables take precedence. Returns immediately with a durable `emailSendId` and the accepted `emailType`. If Sequenzy detects likely missing or unused variables before queueing, the successful response includes a non-blocking `diagnostics` warning object. Missing values do not block queueing or sending; a required variable that is not provided and has no default renders as an empty string.
      *
+     * Select existing identities with senderProfileId or fromEmail (and optional fromName), and replyProfileId or replyTo (with optional replyToName). These inputs look up profiles rather than create them. Use emailType, not isMarketing, to choose delivery policy.
+     *
      * @param {Sequenzy.SendTransactionalRequest} request
      * @param {TransactionalClient.RequestOptions} requestOptions - Request-specific configuration.
      *
@@ -181,6 +198,17 @@ export declare class TransactionalClient {
      *
      * @example
      *     await client.transactional.send({
+     *         html: "<h1>Your week</h1><p>{{SUMMARY}}</p>",
+     *         subject: "Your week in review",
+     *         to: "recipient@example.com",
+     *         trackAs: "weekly-report",
+     *         variables: {
+     *             "SUMMARY": "3 new subscribers"
+     *         }
+     *     })
+     *
+     * @example
+     *     await client.transactional.send({
      *         html: "<p>Connected.</p>",
      *         subject: "Connection test",
      *         to: "recipient@example.com"
@@ -226,14 +254,16 @@ export declare class TransactionalClient {
     send(request: Sequenzy.SendTransactionalRequest, requestOptions?: TransactionalClient.RequestOptions): core.HttpResponsePromise<Sequenzy.SendTransactionalResponse>;
     private __send;
     /**
-     * Updates transactional email metadata or replaces the linked email body using raw HTML or Sequenzy blocks.
+     * Updates transactional email metadata and labels or replaces the linked email body using raw HTML or Sequenzy blocks. Code-managed emails (`managedBy: code`, created by sends with `trackAs`) accept only `name`, `enabled` and `labels`; their content comes from each send, so `subject`, `previewText`, `html` and `blocks` return 400.
      *
      * @param {Sequenzy.UpdateTransactionalRequest} request
      * @param {TransactionalClient.RequestOptions} requestOptions - Request-specific configuration.
      *
      * @throws {@link Sequenzy.BadRequestError}
      * @throws {@link Sequenzy.UnauthorizedError}
+     * @throws {@link Sequenzy.ForbiddenError}
      * @throws {@link Sequenzy.NotFoundError}
+     * @throws {@link Sequenzy.UnprocessableEntityError}
      * @throws {@link Sequenzy.InternalServerError}
      * @throws {@link errors.SequenzyError}
      * @throws {@link errors.SequenzyTimeoutError}

package/dist/esm/api/resources/transactional/client/Client.js

@@ -23,7 +23,9 @@ export class TransactionalClient {
      *
      * @throws {@link Sequenzy.BadRequestError}
      * @throws {@link Sequenzy.UnauthorizedError}
+     * @throws {@link Sequenzy.ForbiddenError}
      * @throws {@link Sequenzy.ConflictError}
+     * @throws {@link Sequenzy.UnprocessableEntityError}
      * @throws {@link Sequenzy.InternalServerError}
      * @throws {@link errors.SequenzyError}
      * @throws {@link errors.SequenzyTimeoutError}
@@ -76,8 +78,12 @@ export class TransactionalClient {
                     throw new Sequenzy.BadRequestError(_response.error.body, _response.rawResponse);
                 case 401:
                     throw new Sequenzy.UnauthorizedError(_response.error.body, _response.rawResponse);
+                case 403:
+                    throw new Sequenzy.ForbiddenError(_response.error.body, _response.rawResponse);
                 case 409:
                     throw new Sequenzy.ConflictError(_response.error.body, _response.rawResponse);
+                case 422:
+                    throw new Sequenzy.UnprocessableEntityError(_response.error.body, _response.rawResponse);
                 case 500:
                     throw new Sequenzy.InternalServerError(_response.error.body, _response.rawResponse);
                 default:
@@ -95,7 +101,7 @@ export class TransactionalClient {
      *
      * Already-sent deliveries are untouched: send history, stats, and stored HTML live on the deliveries themselves.
      *
-     * The email content is kept as a reusable template and returned as `deleted.emailId`; pass that to `DELETE /api/v1/templates/{templateId}` to remove the content too. To stop sends without losing the template, update it with `enabled: false` instead.
+     * The email content is kept as a reusable template and returned as `deleted.emailId`; pass that to `DELETE /api/v1/templates/{templateId}` to remove the content too. Code-managed emails (`managedBy: code`) are the exception: their content snapshot is deleted with them, so the returned `emailId` no longer exists. To stop sends without losing the template, update it with `enabled: false` instead.
      *
      * Requires an API key with the `transactional:delete` scope.
      *
@@ -152,13 +158,7 @@ export class TransactionalClient {
                 case 401:
                     throw new Sequenzy.UnauthorizedError(_response.error.body, _response.rawResponse);
                 case 403:
-                    throw new Sequenzy.ForbiddenError(serializers.Error_.parseOrThrow(_response.error.body, {
-                        unrecognizedObjectKeys: "passthrough",
-                        allowUnrecognizedUnionMembers: true,
-                        allowUnrecognizedEnumValues: true,
-                        skipValidation: true,
-                        breadcrumbsPrefix: ["response"],
-                    }), _response.rawResponse);
+                    throw new Sequenzy.ForbiddenError(_response.error.body, _response.rawResponse);
                 case 404:
                     throw new Sequenzy.NotFoundError(_response.error.body, _response.rawResponse);
                 case 500:
@@ -182,6 +182,7 @@ export class TransactionalClient {
      * @param {TransactionalClient.RequestOptions} requestOptions - Request-specific configuration.
      *
      * @throws {@link Sequenzy.UnauthorizedError}
+     * @throws {@link Sequenzy.ForbiddenError}
      * @throws {@link Sequenzy.NotFoundError}
      * @throws {@link Sequenzy.InternalServerError}
      * @throws {@link Sequenzy.ServiceUnavailableError}
@@ -229,6 +230,8 @@ export class TransactionalClient {
             switch (_response.error.statusCode) {
                 case 401:
                     throw new Sequenzy.UnauthorizedError(_response.error.body, _response.rawResponse);
+                case 403:
+                    throw new Sequenzy.ForbiddenError(_response.error.body, _response.rawResponse);
                 case 404:
                     throw new Sequenzy.NotFoundError(_response.error.body, _response.rawResponse);
                 case 500:
@@ -251,7 +254,10 @@ export class TransactionalClient {
      * @param {Sequenzy.ListTransactionalRequest} request
      * @param {TransactionalClient.RequestOptions} requestOptions - Request-specific configuration.
      *
+     * @throws {@link Sequenzy.BadRequestError}
      * @throws {@link Sequenzy.UnauthorizedError}
+     * @throws {@link Sequenzy.ForbiddenError}
+     * @throws {@link Sequenzy.UnprocessableEntityError}
      * @throws {@link Sequenzy.InternalServerError}
      * @throws {@link Sequenzy.ServiceUnavailableError}
      * @throws {@link errors.SequenzyError}
@@ -264,9 +270,10 @@ export class TransactionalClient {
         return core.HttpResponsePromise.fromPromise(this.__list(request, requestOptions));
     }
     async __list(request = {}, requestOptions) {
-        const { includeMachineEngagement, order, search, sort, status } = request;
+        const { includeMachineEngagement, label, order, search, sort, status } = request;
         const _queryParams = {
             includeMachineEngagement,
+            label,
             order: order != null
                 ? serializers.ListTransactionalRequestOrder.jsonOrThrow(order, {
                     unrecognizedObjectKeys: "strip",
@@ -320,8 +327,14 @@ export class TransactionalClient {
         }
         if (_response.error.reason === "status-code") {
             switch (_response.error.statusCode) {
+                case 400:
+                    throw new Sequenzy.BadRequestError(_response.error.body, _response.rawResponse);
                 case 401:
                     throw new Sequenzy.UnauthorizedError(_response.error.body, _response.rawResponse);
+                case 403:
+                    throw new Sequenzy.ForbiddenError(_response.error.body, _response.rawResponse);
+                case 422:
+                    throw new Sequenzy.UnprocessableEntityError(_response.error.body, _response.rawResponse);
                 case 500:
                     throw new Sequenzy.InternalServerError(_response.error.body, _response.rawResponse);
                 case 503:
@@ -341,12 +354,21 @@ export class TransactionalClient {
      *
      * For callers that may retry, send a stable `Idempotency-Key` header. The same key and request returns the original `emailSendId` for 14 days without another delivery. Reusing a key with different request content returns 409.
      *
+     * Repeated identical transactional content reaching many distinct recipients can trigger a junk/list-testing review. Sending continues while review is pending or unavailable. A substantiated verdict can reject later matching deliveries before sending; these become terminal `failed` sends with an `errorMessage` beginning `Transactional content rejected:`. Read GET /email-sends/{emailSendId} for the final outcome. Failed deliveries are not held or replayed automatically, and replaying the same Idempotency-Key returns the original acceptance response. Dashboard retries of rejected deliveries also fail without sending, even after the decision expires. Correct the content or contact support before deliberately submitting a new logical send. This check does not pause the company or ban the account.
+     *
      * You can either:
      * - Provide a canonical `slug` (or compatibility alias `templateId`) to use a saved template
      * - Provide `subject` and canonical `body` (or compatibility alias `html`) to send custom content directly
      *
      * If both a canonical field and its alias are provided, `slug` must match `templateId` and `body` must match `html`.
      *
+     * **Tracking direct-content sends:**
+     * - Set `trackAs` on a direct-content send (for example `weekly-report`) to count it under one code-managed transactional email. The first send with a new value creates it with `managedBy: code`; later sends with the same value link to it. The value may use up to 255 ASCII letters, digits, spaces and `. _ - : /`, and is normalized like a slug (`Weekly Report` and `weekly-report` are the same email). Other values, including empty ones, return 400 `INVALID_TRACK_AS`.
+     * - Opens, clicks, bounces and the other transactional stats then aggregate on that email, and it appears in `GET /transactional` next to your saved templates. Its subject, preview text and HTML are a snapshot of a recent send, refreshed at most every 10 minutes and stored before variable substitution.
+     * - Disabling the code-managed email makes further sends with that `trackAs` fail with 400 `TRACKED_EMAIL_DISABLED` until you enable it again. Deleting it lets the next send recreate it with fresh stats.
+     * - `trackAs` cannot be combined with `slug`/`templateId`, cannot reuse the slug of a template managed in the dashboard, and a company can have at most 100 code-managed emails. Use a stable name for an email type, never per-recipient values. Code-managed emails cannot be sent by `slug`.
+     * - The email is created after the send passes request validation, so an invalid send does not create it. A send that fails later, for example on an `Idempotency-Key` conflict, can still leave the newly created email with no sends.
+     *
      * **Recipients:**
      * - `to` can be a single email or an array of up to 50 emails
      * - Duplicate emails are automatically deduplicated
@@ -354,16 +376,18 @@ export class TransactionalClient {
      *
      * **Attachments:**
      * - Attachments can be provided as Base64-encoded content or URLs
-     * - Maximum 10 attachments and 7MB total per email
+     * - Maximum 10 attachments and 15MB total per email
      * - Any file type supported (PDFs, images, documents, etc.)
      * - Set `contentId` on an attachment to embed it as an inline image referenced from the HTML as `<img src="cid:VALUE">`
      *
      * A successful response means the email was accepted for background processing. Transactional emails are not blocked by subscriber unsubscribe or double opt-in status. If a recipient is suppressed because of a hard bounce or spam complaint, the worker records the send as `suppressed` instead of delivering it.
      *
      * Optionally set `from` (domain must be verified) and `replyTo` addresses. When reply tracking is enabled, Sequenzy uses a unique trackable `Reply-To` header and treats the resolved reply destination as the forwarding destination for captured replies.
-     * When `replyTo` is omitted, direct-content sends inherit the company's default reply profile and saved-template sends prefer the template reply profile before the company default. Both fall back to the first company reply profile. The resolved destination is retained whether or not reply tracking is enabled; it is sent as the Reply-To header only when reply tracking is disabled.
+     * Without a reply identity override, saved-template sends prefer the template reply profile. Otherwise sends prefer the effective sending domain's default reply profile, then the company default, then the first company reply profile. The resolved destination is retained whether or not reply tracking is enabled; it is sent as the Reply-To header only when reply tracking is disabled.
      * Variables can be passed to customize the email content. Nested objects and arrays are supported for repeat blocks, such as `items`. `{{viewInBrowserUrl}}` is generated automatically for a hosted copy link. For a single recipient, Sequenzy matches an existing subscriber by `subscriberExternalId` or email and backfills stored first and last names when the corresponding request variables are omitted; explicit variables take precedence. Returns immediately with a durable `emailSendId` and the accepted `emailType`. If Sequenzy detects likely missing or unused variables before queueing, the successful response includes a non-blocking `diagnostics` warning object. Missing values do not block queueing or sending; a required variable that is not provided and has no default renders as an empty string.
      *
+     * Select existing identities with senderProfileId or fromEmail (and optional fromName), and replyProfileId or replyTo (with optional replyToName). These inputs look up profiles rather than create them. Use emailType, not isMarketing, to choose delivery policy.
+     *
      * @param {Sequenzy.SendTransactionalRequest} request
      * @param {TransactionalClient.RequestOptions} requestOptions - Request-specific configuration.
      *
@@ -420,6 +444,17 @@ export class TransactionalClient {
      *
      * @example
      *     await client.transactional.send({
+     *         html: "<h1>Your week</h1><p>{{SUMMARY}}</p>",
+     *         subject: "Your week in review",
+     *         to: "recipient@example.com",
+     *         trackAs: "weekly-report",
+     *         variables: {
+     *             "SUMMARY": "3 new subscribers"
+     *         }
+     *     })
+     *
+     * @example
+     *     await client.transactional.send({
      *         html: "<p>Connected.</p>",
      *         subject: "Connection test",
      *         to: "recipient@example.com"
@@ -527,14 +562,16 @@ export class TransactionalClient {
         return handleNonStatusCodeError(_response.error, _response.rawResponse, "POST", "/transactional/send");
     }
     /**
-     * Updates transactional email metadata or replaces the linked email body using raw HTML or Sequenzy blocks.
+     * Updates transactional email metadata and labels or replaces the linked email body using raw HTML or Sequenzy blocks. Code-managed emails (`managedBy: code`, created by sends with `trackAs`) accept only `name`, `enabled` and `labels`; their content comes from each send, so `subject`, `previewText`, `html` and `blocks` return 400.
      *
      * @param {Sequenzy.UpdateTransactionalRequest} request
      * @param {TransactionalClient.RequestOptions} requestOptions - Request-specific configuration.
      *
      * @throws {@link Sequenzy.BadRequestError}
      * @throws {@link Sequenzy.UnauthorizedError}
+     * @throws {@link Sequenzy.ForbiddenError}
      * @throws {@link Sequenzy.NotFoundError}
+     * @throws {@link Sequenzy.UnprocessableEntityError}
      * @throws {@link Sequenzy.InternalServerError}
      * @throws {@link errors.SequenzyError}
      * @throws {@link errors.SequenzyTimeoutError}
@@ -588,8 +625,12 @@ export class TransactionalClient {
                     throw new Sequenzy.BadRequestError(_response.error.body, _response.rawResponse);
                 case 401:
                     throw new Sequenzy.UnauthorizedError(_response.error.body, _response.rawResponse);
+                case 403:
+                    throw new Sequenzy.ForbiddenError(_response.error.body, _response.rawResponse);
                 case 404:
                     throw new Sequenzy.NotFoundError(_response.error.body, _response.rawResponse);
+                case 422:
+                    throw new Sequenzy.UnprocessableEntityError(_response.error.body, _response.rawResponse);
                 case 500:
                     throw new Sequenzy.InternalServerError(_response.error.body, _response.rawResponse);
                 default:

package/dist/esm/api/resources/transactional/client/requests/CreateTransactionalRequest.d.ts

@@ -8,13 +8,15 @@ import type * as Sequenzy from "../../../../index.js";
 export interface CreateTransactionalRequest extends Sequenzy.EmailBodyInput {
     /** Defaults to false with prompt and true with explicit HTML or blocks. */
     enabled?: boolean;
+    /** Company label names. Trimmed and deduplicated; missing names are created. Replaces all assignments; [] clears them. Omit to preserve assignments on update or start without labels on create. Null and blank names are rejected. */
+    labels?: string[];
     name: string;
     previewText?: string | null;
     /** Natural-language request for branded transactional blocks. */
     prompt?: string;
     /** Optional API slug used when sending by slug. If omitted, one is generated from the name. */
     slug?: string;
-    /** Generation style; valid only with prompt. */
+    /** Generation style; valid only with prompt. Pass designed or plain to force the designed or plain-text email style; other values are freeform prompt guidance. Defaults to the company's email style preference. */
     style?: string;
     /** Required with HTML or blocks; optional with prompt, where it overrides the generated subject. */
     subject?: string;

package/dist/esm/api/resources/transactional/client/requests/ListTransactionalRequest.d.ts

@@ -6,6 +6,8 @@ import type * as Sequenzy from "../../../../index.js";
 export interface ListTransactionalRequest {
     /** Include detected bot, scanner, preview, and privacy-proxy engagement in open and click metrics. */
     includeMachineEngagement?: boolean;
+    /** Filter by company label names, matching any. Repeat the parameter for multiple names; commas are literal characters. Combined with search and status. Unknown names match no templates. */
+    label?: string | string[];
     /** Sort direction. */
     order?: Sequenzy.ListTransactionalRequestOrder;
     /** Case-insensitive search across template name, API slug, and linked email subject/title. */

package/dist/esm/api/resources/transactional/client/requests/SendTransactionalRequest.d.ts

@@ -43,6 +43,17 @@ import type * as Sequenzy from "../../../../index.js";
  *
  * @example
  *     {
+ *         html: "<h1>Your week</h1><p>{{SUMMARY}}</p>",
+ *         subject: "Your week in review",
+ *         to: "recipient@example.com",
+ *         trackAs: "weekly-report",
+ *         variables: {
+ *             "SUMMARY": "3 new subscribers"
+ *         }
+ *     }
+ *
+ * @example
+ *     {
  *         html: "<p>Connected.</p>",
  *         subject: "Connection test",
  *         to: "recipient@example.com"
@@ -95,7 +106,7 @@ export interface SendTransactionalRequest {
      *
      * Set `contentId` to embed the file as an inline image the HTML references with `<img src="cid:VALUE">` instead of attaching it.
      *
-     * Maximum 10 attachments and 7MB total per email.
+     * Maximum 10 attachments and 15MB total per email.
      */
     attachments?: Sequenzy.Attachment[];
     /** Blind-carbon-copy recipient email address(es). Duplicates already present in `to` or `cc` are removed. */
@@ -109,18 +120,31 @@ export interface SendTransactionalRequest {
     /**
      * Custom from address. Format: "Name <email>" or just "email".
      * The domain must be verified for your account. If not verified, this field is silently ignored.
+     * When the address exactly matches an existing sender identity (the display name disambiguates if
+     * several identities share the address), that identity - including its sending route - is used for
+     * the send; otherwise the template or company-default identity is kept and this field only changes
+     * the visible From.
+     *  Mutually exclusive with senderProfileId, fromEmail and fromName.
      */
     from?: string;
+    /** Address of an existing verified sender profile in this company. Mutually exclusive with senderProfileId and from. If several identities share the address, select one with fromName. */
+    fromEmail?: string;
+    /** Display name selecting an existing identity on fromEmail. Requires fromEmail; mutually exclusive with senderProfileId and from. Does not create a profile. */
+    fromName?: string;
+    /** Extra email headers as header name to string value, up to 50 applied. Names use letters, digits and hyphens (max 100 characters); values are one line of printable ASCII and each `Name: value` line fits in 998 characters. A transactional send can carry your own `List-Unsubscribe`, plus `List-Unsubscribe-Post: List-Unsubscribe=One-Click` for RFC 8058 one-click unsubscribe; unsubscribes through your link are not suppressed in Sequenzy. Marketing sends always use Sequenzy's signed unsubscribe headers, so `List-Unsubscribe`, `List-Unsubscribe-Post`, `Precedence` and `Feedback-ID` are not applied. Headers Sequenzy manages (From, Sender, To, Cc, Bcc, Reply-To, Subject, Date, Message-ID, MIME-Version, Return-Path, Received, Received-SPF, Delivered-To, DKIM-Signature, Authentication-Results, and names starting with Content-, X-Sequenzy-, X-SES-, ARC- or Resent-) are never applied. A header that cannot be applied never fails the request; it is listed in the response `ignoredHeaders`. Names match case-insensitively; when names differ only in case, only the first one is considered, even if it is not applied. A retry of a failed delivery (dashboard or outage recovery) resends without these headers. */
+    headers?: Record<string, string>;
     /** Compatibility alias for `body`. Accepted with `subject` for direct sends and must match `body` when both are provided. */
     html?: string;
     /** Preview text for the email (only used with direct content) */
     preview?: string;
-    /**
-     * Reply-to address. Format: "Name <email>" or just "email".
-     * Can be any valid email address. When reply tracking is disabled, this value is sent as the email's `Reply-To` header. When reply tracking is enabled, Sequenzy sends a unique trackable `Reply-To` header and stores this value as the forwarding destination for replies.
-     * When omitted, direct-content sends inherit the company default and saved-template sends prefer the template reply profile before the company default. Both fall back to the first company reply profile. The resolved destination is retained whether or not reply tracking is enabled; it is sent directly only when reply tracking is disabled.
-     */
+    /** Existing reply profile ID. Mutually exclusive with replyTo and replyToName. Overrides the saved template and default reply identity. */
+    replyProfileId?: string;
+    /** Reply-to address as "Name <email>" or a bare email, optionally paired with replyToName. Mutually exclusive with replyProfileId. With reply tracking enabled, Sequenzy sends a trackable Reply-To and stores this address as its forwarding destination. Without a reply override, saved-template sends prefer the template reply profile; otherwise sends prefer the effective sending-domain default, then company default, then the first company reply profile. */
     replyTo?: string;
+    /** Display name for a bare replyTo address. Requires replyTo and is mutually exclusive with replyProfileId. Does not create a profile. */
+    replyToName?: string;
+    /** Existing verified sender profile ID. Mutually exclusive with fromEmail, fromName and from. Selects that identity and its sending route; does not create a profile. */
+    senderProfileId?: string;
     /** Canonical slug of the transactional email template to use (mutually exclusive with direct content). */
     slug?: string;
     /** Email subject (required if not using slug) */
@@ -131,7 +155,9 @@ export interface SendTransactionalRequest {
     templateId?: string;
     /** Recipient email address(es). Can be a single email string or an array of up to 50 emails. */
     to: Sequenzy.SendTransactionalRequestTo;
-    /** Per-send tracking opt-outs. Each field defaults to `true`, meaning your account's tracking settings apply; set a field to `false` to disable that tracking for this send only. These fields can only opt out; they cannot enable tracking that is disabled for your account. */
+    /** Direct content only. Names the email type so its sends are counted under one code-managed transactional email, created on first use. Up to 255 ASCII letters, digits, spaces and `. _ - : /`, including at least one letter or digit; it is normalized like a slug. Cannot be combined with `slug`/`templateId`. */
+    trackAs?: string;
+    /** Per-send tracking opt-outs. Omitted fields follow the company Transactional API open/click defaults. Set false to disable tracking for this send. Neither true nor omission can enable tracking disabled by account-wide or Transactional API settings. */
     trackingSettings?: Sequenzy.SendTransactionalRequestTrackingSettings;
     /** Variables for template replacement (works with both modes). Values can be scalars, nested objects, or arrays used by repeat blocks. For a single recipient, stored subscriber first and last names fill missing name variables; explicit request variables take precedence. Raw HTML templates can use simple subscriber/custom-attribute conditionals such as `{{#if subscriber.plan}}...{{else}}...{{/if}}` and `{{#unless subscriber.plan}}...{{/unless}}`. Variables are always HTML-escaped; a template can prefix a tag with `html.` (`{{html.prerenderedHtml}}`) to insert a trusted HTML value unescaped. Injected HTML is sanitized (scripts, event handlers, and dangerous URLs are stripped), only applies in HTML text position, and must not contain end-user input. Likely variable issues are returned as non-blocking diagnostics when possible; missing required variables without defaults render as empty strings and do not block sending. */
     variables?: Record<string, unknown>;

package/dist/esm/api/resources/transactional/client/requests/UpdateTransactionalRequest.d.ts

@@ -9,6 +9,8 @@ export interface UpdateTransactionalRequest extends Sequenzy.EmailBodyInput {
     /** Transactional email ID or slug */
     idOrSlug: string;
     enabled?: boolean;
+    /** Company label names. Trimmed and deduplicated; missing names are created. Replaces all assignments; [] clears them. Omit to preserve assignments on update or start without labels on create. Null and blank names are rejected. */
+    labels?: string[];
     name?: string;
     previewText?: string | null;
     subject?: string;

package/dist/esm/api/resources/transactional/types/DeleteTransactionalResponseDeleted.d.ts

@@ -1,5 +1,7 @@
 export interface DeleteTransactionalResponseDeleted {
-    /** The email content kept as a reusable template. Delete it separately with `DELETE /api/v1/templates/{templateId}`. */
+    /** True when the content was deleted with the email (code-managed emails, whose content is a snapshot of a real send). False when it was kept as a reusable template. */
+    emailDeleted?: boolean;
+    /** The email content kept as a reusable template. Delete it separately with `DELETE /api/v1/templates/{templateId}`. For a code-managed email this id no longer exists; see `emailDeleted`. */
     emailId?: string;
     id?: string;
     name?: string;

package/dist/esm/api/resources/transactional/types/SendTransactionalRequestTrackingSettings.d.ts

@@ -1,5 +1,5 @@
 /**
- * Per-send tracking opt-outs. Each field defaults to `true`, meaning your account's tracking settings apply; set a field to `false` to disable that tracking for this send only. These fields can only opt out; they cannot enable tracking that is disabled for your account.
+ * Per-send tracking opt-outs. Omitted fields follow the company Transactional API open/click defaults. Set false to disable tracking for this send. Neither true nor omission can enable tracking disabled by account-wide or Transactional API settings.
  */
 export interface SendTransactionalRequestTrackingSettings {
     /** Set `false` to skip link rewriting so the original URLs are delivered unchanged. Useful when the click-tracking redirect domain breaks iOS/Android universal links or deep links in transactional emails. */

package/dist/esm/api/resources/transactional/types/SendTransactionalResponse.d.ts

@@ -1,2 +1,2 @@
 import type * as Sequenzy from "../../../index.js";
-export type SendTransactionalResponse = Sequenzy.SendTransactionalResponseTransactional | Sequenzy.SendTransactionalResponseOne;
+export type SendTransactionalResponse = Sequenzy.SendTransactionalResponseZero | Sequenzy.SendTransactionalResponseOne;

package/dist/esm/api/resources/transactional/types/SendTransactionalResponseOne.d.ts

@@ -1,5 +1,9 @@
 import type * as Sequenzy from "../../../index.js";
 export interface SendTransactionalResponseOne {
+    /** Deduplicated BCC recipients; omitted when empty. */
+    bcc?: string[];
+    /** Deduplicated CC recipients; omitted when empty. */
+    cc?: string[];
     diagnostics?: Sequenzy.TransactionalSendDiagnostics;
     /** Durable email delivery ID. Use this with GET /email-sends/{emailSendId}. */
     emailSendId?: string;
@@ -7,8 +11,11 @@ export interface SendTransactionalResponseOne {
     emailType?: Sequenzy.SendTransactionalResponseOneEmailType;
     /** True when this response replays an earlier request with the same Idempotency-Key. */
     idempotentReplay?: boolean;
+    ignoredHeaders?: Sequenzy.TransactionalSendIgnoredHeaders;
     /** Legacy queue identifier retained for response compatibility. */
     jobId?: string;
     success?: boolean;
     to?: Sequenzy.SendTransactionalResponseOneTo;
+    /** Code-managed transactional email the send is counted under. Present only when the request set `trackAs`. */
+    transactional?: Sequenzy.SendTransactionalResponseOneTransactional;
 }

package/dist/esm/api/resources/transactional/types/SendTransactionalResponseOneTransactional.d.ts

@@ -0,0 +1,8 @@
+/**
+ * Code-managed transactional email the send is counted under. Present only when the request set `trackAs`.
+ */
+export interface SendTransactionalResponseOneTransactional {
+    id?: string;
+    name?: string;
+    slug?: string;
+}

package/dist/esm/api/resources/transactional/types/SendTransactionalResponseOneTransactional.js

@@ -0,0 +1,2 @@
+// This file was auto-generated by Fern from our API Definition.
+export {};

package/dist/esm/api/resources/transactional/types/SendTransactionalResponseZero.d.ts

@@ -0,0 +1,20 @@
+import type * as Sequenzy from "../../../index.js";
+export interface SendTransactionalResponseZero {
+    /** Deduplicated BCC recipients; omitted when empty. */
+    bcc?: string[];
+    /** Deduplicated CC recipients; omitted when empty. */
+    cc?: string[];
+    diagnostics?: Sequenzy.TransactionalSendDiagnostics;
+    /** Durable email delivery ID. Use this with GET /email-sends/{emailSendId}. */
+    emailSendId?: string;
+    /** Delivery policy accepted for the queued email. */
+    emailType?: Sequenzy.SendTransactionalResponseZeroEmailType;
+    /** True when this response replays an earlier request with the same Idempotency-Key. */
+    idempotentReplay?: boolean;
+    ignoredHeaders?: Sequenzy.TransactionalSendIgnoredHeaders;
+    /** Legacy queue identifier retained for response compatibility. */
+    jobId?: string;
+    success?: boolean;
+    to?: Sequenzy.SendTransactionalResponseZeroTo;
+    transactional?: Sequenzy.SendTransactionalResponseZeroTransactional;
+}

package/dist/esm/api/resources/transactional/types/SendTransactionalResponseZero.js

@@ -0,0 +1,2 @@
+// This file was auto-generated by Fern from our API Definition.
+export {};

package/dist/esm/api/resources/transactional/types/SendTransactionalResponseZeroEmailType.d.ts

@@ -0,0 +1,6 @@
+/** Delivery policy accepted for the queued email. */
+export declare const SendTransactionalResponseZeroEmailType: {
+    readonly Marketing: "marketing";
+    readonly Transactional: "transactional";
+};
+export type SendTransactionalResponseZeroEmailType = (typeof SendTransactionalResponseZeroEmailType)[keyof typeof SendTransactionalResponseZeroEmailType];

package/dist/esm/api/resources/transactional/types/SendTransactionalResponseZeroEmailType.js

@@ -0,0 +1,6 @@
+// This file was auto-generated by Fern from our API Definition.
+/** Delivery policy accepted for the queued email. */
+export const SendTransactionalResponseZeroEmailType = {
+    Marketing: "marketing",
+    Transactional: "transactional",
+};

package/dist/esm/api/resources/transactional/types/SendTransactionalResponseZeroTo.d.ts

@@ -0,0 +1 @@
+export type SendTransactionalResponseZeroTo = string | string[];

package/dist/esm/api/resources/transactional/types/SendTransactionalResponseZeroTo.js

@@ -0,0 +1,2 @@
+// This file was auto-generated by Fern from our API Definition.
+export {};

package/dist/esm/api/resources/transactional/types/SendTransactionalResponseZeroTransactional.d.ts

@@ -0,0 +1,5 @@
+export interface SendTransactionalResponseZeroTransactional {
+    id?: string;
+    name?: string;
+    slug?: string;
+}

package/dist/esm/api/resources/transactional/types/SendTransactionalResponseZeroTransactional.js

@@ -0,0 +1,2 @@
+// This file was auto-generated by Fern from our API Definition.
+export {};

package/dist/esm/api/resources/transactional/types/index.d.ts

@@ -15,8 +15,9 @@ export * from "./SendTransactionalResponse.js";
 export * from "./SendTransactionalResponseOne.js";
 export * from "./SendTransactionalResponseOneEmailType.js";
 export * from "./SendTransactionalResponseOneTo.js";
-export * from "./SendTransactionalResponseTransactional.js";
-export * from "./SendTransactionalResponseTransactionalEmailType.js";
-export * from "./SendTransactionalResponseTransactionalTo.js";
-export * from "./SendTransactionalResponseTransactionalTransactional.js";
+export * from "./SendTransactionalResponseOneTransactional.js";
+export * from "./SendTransactionalResponseZero.js";
+export * from "./SendTransactionalResponseZeroEmailType.js";
+export * from "./SendTransactionalResponseZeroTo.js";
+export * from "./SendTransactionalResponseZeroTransactional.js";
 export * from "./UpdateTransactionalResponse.js";

package/dist/esm/api/resources/transactional/types/index.js

@@ -15,8 +15,9 @@ export * from "./SendTransactionalResponse.js";
 export * from "./SendTransactionalResponseOne.js";
 export * from "./SendTransactionalResponseOneEmailType.js";
 export * from "./SendTransactionalResponseOneTo.js";
-export * from "./SendTransactionalResponseTransactional.js";
-export * from "./SendTransactionalResponseTransactionalEmailType.js";
-export * from "./SendTransactionalResponseTransactionalTo.js";
-export * from "./SendTransactionalResponseTransactionalTransactional.js";
+export * from "./SendTransactionalResponseOneTransactional.js";
+export * from "./SendTransactionalResponseZero.js";
+export * from "./SendTransactionalResponseZeroEmailType.js";
+export * from "./SendTransactionalResponseZeroTo.js";
+export * from "./SendTransactionalResponseZeroTransactional.js";
 export * from "./UpdateTransactionalResponse.js";