sinfactura-types 1.10.449 → 1.10.451

package/dist/afip.d.ts

@@ -142,5 +142,46 @@ declare global {
      * certificate at the one moment the operator is uploading it.
      */
     type AfipCertUploadErrorCode = 'AFIP_CERT_NOT_A_CERTIFICATE' | 'AFIP_KEY_NOT_A_PRIVATE_KEY' | 'AFIP_CERT_CUIT_MISSING' | 'AFIP_CERT_CUIT_UNREADABLE' | 'AFIP_CERT_CUIT_MISMATCH' | 'AFIP_CERT_KEY_MISMATCH' | 'AFIP_CERT_EXPIRED';
+    /**
+     * The body of `POST /afip { mode: 'upload' }` — ONE half of the AFIP
+     * credential per request: the X.509 certificate (`cert`) or the private key
+     * (`key`), never both. The success answer is `{ message }` with no `data`;
+     * nothing uploaded is ever echoed back.
+     *
+     * A half counts as PRESENT only when its string is over 200 characters; a
+     * shorter one (an empty string included) is treated exactly as absent. So a
+     * body with neither half present is refused `400 AFIP_CERT_OR_KEY_MISSING` —
+     * a short `cert` of garbage gets that code, never
+     * `AFIP_CERT_NOT_A_CERTIFICATE` — and one with both present
+     * `400 AFIP_CERT_AND_KEY_TOGETHER`, while `{ cert: '', key: <PEM> }` is an
+     * ordinary key upload. A body that fails the schema (a non-string half, a
+     * non-boolean `rotate`) is refused `400 VALIDATION_FAILED` before any of
+     * that. Every other refusal comes from the upload pre-flight (file parse,
+     * store CUIT, keypair, expiry), coded by `AfipCertUploadErrorCode`.
+     *
+     * ⚠️ **A KEY upload blanks the stored certificate**, so a key that is not the
+     * stored certificate's keypair is refused `400 AFIP_CERT_KEY_MISMATCH` —
+     * UNLESS the body says `rotate: true`. With it the key is accepted, the stored
+     * certificate is blanked, and the next certificate upload is checked against
+     * the NEW key. That is how a tenant rotates an externally generated keypair:
+     * key first with `rotate: true`, then the certificate issued for it.
+     * Without the flag a rotation is impossible in either order.
+     *
+     * `rotate` is typed `boolean` because the endpoint accepts `false`, which
+     * means exactly what absent means. It is ignored on a certificate upload.
+     *
+     * Tied to the handler's Zod schema (minus `mode`, which the dispatch table
+     * consumes) by `AssertAfipCertUploadRequestMatchesSchema` in
+     * `stacks/lambdas/afip/_upload.ts`.
+     */
+    interface AfipCertUploadRequest {
+        mode: 'upload';
+        /** PEM private key. Encrypted at rest; never returned by any endpoint. */
+        key?: string;
+        /** PEM X.509 certificate. */
+        cert?: string;
+        /** Confirms a KEY upload as a deliberate keypair rotation. See above. */
+        rotate?: boolean;
+    }
 }
 export {};

package/dist/ai.d.ts

@@ -71,6 +71,23 @@ declare global {
      * `0`, because `0` is a value an operator would accept without checking.
      */
     interface SupplierDocExtractItem {
+        /**
+         * The supplier's own product code for this line, as printed, trimmed.
+         * Absent when the line prints none — never `''`.
+         *
+         * A JOIN KEY that survives a misread `description`: match the line to a
+         * purchase-order line on `barcode`, then `sku`, then name. Additive — a
+         * line extracted before this field existed simply lacks it.
+         */
+        sku?: string;
+        /**
+         * The printed barcode (EAN/UPC), reduced to its DIGITS — spaces, dashes
+         * and any other character are removed server-side. Absent when the line
+         * prints none, or nothing numeric survives — never `''`. Its length is
+         * NOT validated as an EAN/UPC here: it is a join key, and a misread value
+         * simply fails to match, so fall back to `sku`, then name.
+         */
+        barcode?: string;
         /**
          * The line's description as printed.
          *

package/dist/api.d.ts

@@ -25,8 +25,14 @@ declare global {
          *   `Query`. Can be a NUMBER when the query rides a GSI with a numeric
          *   sort key (e.g. `GET /invoices`' date branch yields `dated` as a number).
          * - **Opaque string** — a base64url cursor the caller round-trips back
-         *   unparsed as `?startKey=` (e.g. `GET /suppliers?mode=invoices`),
-         *   derived from the last RETURNED row, never a raw `LastEvaluatedKey`.
+         *   unparsed as `?startKey=` (e.g. `GET /suppliers?mode=invoices`,
+         *   `GET /customers`). Where it resumes is the endpoint's business and is
+         *   NOT always the last returned row: a walk that stopped because its page
+         *   filled resumes after the last RETURNED row, while one that stopped on
+         *   its read budget resumes from DynamoDB's own `LastEvaluatedKey` — the
+         *   read head, past rows its filter dropped (`deriveResumeKey`,
+         *   `stacks/helpers/opaqueCursor.ts`). Some cursors are also bound to the
+         *   filters they were issued under and refused `INVALID_CURSOR` otherwise.
          *
          * Consumers must not assume this is enumerable — treat the string form
          * as opaque and pass it straight back.

package/dist/cjs/whatsapp.js

@@ -1,6 +1,7 @@
 "use strict";
 /**
- * Published WhatsApp surface — the tenant-facing connection config only.
+ * Published WhatsApp surface — the tenant-facing connection config and the
+ * tenant's own template send (`POST /whatsapp/send`).
  *
  * ⚠️ **Meta's inbound webhook payload is NOT here and must not come back.**
  * The twelve shapes Meta POSTs to `/whatsapp` — the entry/change/value
@@ -14,3 +15,56 @@
  * against `lib.dom`'s `Document`, returning `undefined` at runtime.
  */
 Object.defineProperty(exports, "__esModule", { value: true });
+exports.WHATSAPP_SEND_ERROR_CODES = void 0;
+/**
+ * `POST /whatsapp/send` refusals, beyond the cross-cutting `GATING_ERROR_CODES`
+ * (notably `PLAN_LIMIT_EXCEEDED` for the `whatsappMessages` monthly cap).
+ *
+ * - `VALIDATION_FAILED` · 400 — including a body naming both or neither of
+ *   `to` / `customerId`.
+ * - `IDEMPOTENCY_KEY_REQUIRED` · 400 — no `Idempotency-Key` header. The
+ *   idempotency wrapper's own codes (`INVALID_IDEMPOTENCY_KEY`,
+ *   `IDEMPOTENCY_KEY_REUSE`, `IDEMPOTENCY_IN_PROGRESS`, `IDEMPOTENCY_KEY_FAILED`,
+ *   `IDEMPOTENCY_LOCK_CONTENTION`) apply too. `IDEMPOTENCY_KEY_FAILED` (409)
+ *   means an earlier attempt under this key may have reached Meta: check the
+ *   recipient's chat before sending again under a NEW key.
+ * - `PLATFORM_INTEGRATION_DISABLED` · 503 — WhatsApp is switched off
+ *   platform-wide by SINFACTURA.
+ * - `WHATSAPP_NOT_CONNECTED` · 409 — the calling store has no connected
+ *   WhatsApp, or a connection with no stored token after a disconnect. Disable
+ *   the send control. ⚠️ Never falls back to the platform number.
+ * - `WHATSAPP_TOKEN_REJECTED` · 409 — connected, but Meta refused the stored
+ *   token. Reconnect.
+ * - `CUSTOMER_NOT_FOUND` · 404 / `WHATSAPP_RECIPIENT_PHONE_MISSING` · 400 — a bad
+ *   id versus a real customer with no usable number.
+ * - `WHATSAPP_RECIPIENT_NOT_ALLOWED` · 403 — non-production stages only: the
+ *   number is not on that stage's test allowlist. Nothing was sent.
+ * - `WHATSAPP_TEMPLATE_NOT_APPROVED` · 422 — not approved, paused, disabled,
+ *   wrong language or wrong parameter count (Meta does not tell these apart).
+ * - `WHATSAPP_RECIPIENT_OPTED_OUT` · 409 — the recipient cannot receive it.
+ * - `WHATSAPP_RATE_LIMITED` · 429 — throughput cap; retry later.
+ * - `WHATSAPP_ACCOUNT_SUSPENDED` · 403 — the WhatsApp Business account or the
+ *   number itself is restricted.
+ * - `WHATSAPP_SEND_FAILED` · 502 — any other Meta 4xx refusal; carries `metaCode`.
+ * - `WHATSAPP_SEND_UNCONFIRMED` · 502 — the request reached Meta and its outcome
+ *   is unknown: no answer came back, Meta answered 5xx, or Meta accepted it
+ *   without a message id.
+ *   The message may have been delivered, so the key is sealed:
+ *   a retry under it answers `IDEMPOTENCY_KEY_FAILED` rather than re-sending.
+ */
+exports.WHATSAPP_SEND_ERROR_CODES = [
+    'VALIDATION_FAILED',
+    'IDEMPOTENCY_KEY_REQUIRED',
+    'PLATFORM_INTEGRATION_DISABLED',
+    'WHATSAPP_NOT_CONNECTED',
+    'WHATSAPP_TOKEN_REJECTED',
+    'CUSTOMER_NOT_FOUND',
+    'WHATSAPP_RECIPIENT_PHONE_MISSING',
+    'WHATSAPP_RECIPIENT_NOT_ALLOWED',
+    'WHATSAPP_TEMPLATE_NOT_APPROVED',
+    'WHATSAPP_RECIPIENT_OPTED_OUT',
+    'WHATSAPP_RATE_LIMITED',
+    'WHATSAPP_ACCOUNT_SUSPENDED',
+    'WHATSAPP_SEND_FAILED',
+    'WHATSAPP_SEND_UNCONFIRMED',
+];

package/dist/customer.d.ts

@@ -57,6 +57,56 @@ declare global {
     }
     /** Write shape for customer create/update — carries the transient photo controls. */
     type CustomerUpsertInput = Partial<Customer> & PhotoUploadControls;
+    /**
+     * The query string of the customers LIST read — `GET /customers` with no
+     * `customerId`, `list` or `email`. Every present filter AND-composes: a row is
+     * returned only when it matches all of them. The store's system customer is
+     * never listed, and rows come back newest first.
+     *
+     * Answered as a `ResponseApi` whose `data` is an array of display-projected
+     * rows (`customerId` plus the list's display fields — never the commercial or
+     * fiscal terms, which only the `customerId` point read serves), with an opaque
+     * cursor in `LastEvaluatedKey` and `truncated: true` present EXACTLY when a
+     * cursor is — a page that stopped before the store's customers ran out carries
+     * both, the last page carries neither.
+     *
+     * ⚠️ Refusals, all `400` and all before any read:
+     * - `INVALID_FILTER`, with `data.param` naming the parameter, for a value outside
+     *   a chip's set or a `limit` outside 1–100. An unknown value is never ignored:
+     *   ignoring it answered the unfiltered list under a lit chip.
+     * - `INVALID_CURSOR` for a `startKey` that is malformed, belongs to another store,
+     *   or was issued under DIFFERENT filters. The cursor is bound to the filters it
+     *   was minted with (the search compared after accent and case folding, `limit`
+     *   excluded), so a client that changes a filter must restart from page one.
+     *   Treat it as a stall, not a failure.
+     *
+     * An EMPTY value (`?withBuy=`) is the same as an absent one.
+     */
+    interface CustomerListQuery {
+        /**
+         * Free-text terms matched against the customer's search index — accent- and
+         * case-insensitive, up to four terms, every term required. A value that
+         * folds to no term is no search.
+         */
+        search?: string;
+        /**
+         * The soft-delete set. Absent or `'false'`: enabled customers only (a row
+         * that never carried the flag counts as enabled). `'true'`: disabled only.
+         * `'all'`: both.
+         */
+        disabled?: 'true' | 'false' | 'all';
+        /** `'true'`: customers who have bought at least once. `'false'`: never bought. */
+        withBuy?: 'true' | 'false';
+        /**
+         * `'owing'`: a positive balance, i.e. the customer owes the store.
+         * `'nonzero'`: any non-zero balance, in either direction.
+         */
+        balance?: 'owing' | 'nonzero';
+        /** Rows per page, 1–100. Absent: a page of 1000 rows. */
+        limit?: number;
+        /** The previous page's `LastEvaluatedKey`, sent back unchanged under the SAME filters. */
+        startKey?: string;
+    }
     /**
      * One unsettled debit on a customer's current account, as denormalised onto
      * the `Customer` row for the accounts report's aging summary.

package/dist/subscription.d.ts

@@ -85,7 +85,7 @@ declare global {
      * exhausts this union (a `switch`, a `Record<FeatureKey, …>`) still has to
      * handle the new member in the same change.
      */
-    type FeatureKey = 'maxOrdersMonth' | 'maxInvoicesMonth' | 'maxProducts' | 'maxUsers' | 'maxCustomers' | 'maxWarehouses' | 'priceListsMax' | 'webhooks' | 'afipInvoicing' | 'suppliers' | 'domesticPayments' | 'stripePayments' | 'cashManagement' | 'importExport' | 'advancedReports' | 'customBranding' | 'prioritySupport' | 'whatsappCommerce' | 'aiFeatures' | 'mobileApp' | 'customDomain' | 'advancedPricing' | 'marketplaceChannels' | 'storefront' | 'loyalty' | 'marketing' | 'mandatory2fa';
+    type FeatureKey = 'maxOrdersMonth' | 'maxInvoicesMonth' | 'whatsappMessages' | 'maxProducts' | 'maxUsers' | 'maxCustomers' | 'maxWarehouses' | 'priceListsMax' | 'webhooks' | 'afipInvoicing' | 'suppliers' | 'domesticPayments' | 'stripePayments' | 'cashManagement' | 'importExport' | 'advancedReports' | 'customBranding' | 'prioritySupport' | 'whatsappCommerce' | 'aiFeatures' | 'mobileApp' | 'customDomain' | 'advancedPricing' | 'marketplaceChannels' | 'storefront' | 'loyalty' | 'marketing' | 'mandatory2fa';
     /** Resolved entitlements for a specific tenant (matrix + overrides applied). */
     type ResolvedEntitlements = Record<FeatureKey, Entitlement>;
     /**

package/dist/webhook.d.ts

@@ -142,6 +142,78 @@ export interface Webhook {
     consecutiveFailures: number;
     entityType: 'WEBHOOK';
 }
+/**
+ * A subscription as the list (`GET …/webhooks`) returns it: an ALLOW-LIST
+ * projection of {@link Webhook}. No `storeId`, no `search`, no `entityType` —
+ * and never the signing key, which no read returns.
+ */
+export type PublicWebhook = Pick<Webhook, 'webhookId' | 'url' | 'events' | 'active' | 'description' | 'createdAt' | 'updatedAt' | 'lastDeliveryAt' | 'lastError' | 'consecutiveFailures'>;
+/**
+ * The body of `POST …/webhooks` — a create when `webhookId` is ABSENT, an
+ * update of that webhook when present. Omit the key entirely to create; an
+ * unknown `webhookId` is `404 WEBHOOK_NOT_FOUND`, never a create.
+ *
+ * `active` defaults to `true` on a create and to the stored value on an
+ * update. An update never re-mints the signing secret — that is
+ * `…/rotate-secret`, and nothing else.
+ *
+ * Tied to the handler's Zod schema by `AssertWebhookUpsertRequestMatchesSchema`
+ * in `stacks/lambdas/tenants/_webhooks.ts`.
+ */
+export interface WebhookUpsertRequest {
+    /** Max 64 characters. */
+    webhookId?: string;
+    /** A URL, max 2048 characters, and must pass the egress check. */
+    url: string;
+    /** At least one. */
+    events: WebhookEventType[];
+    active?: boolean;
+    /** Max 500 characters. */
+    description?: string;
+}
+/**
+ * `data` of `POST …/webhooks`.
+ *
+ * ⚠️ `secret` is the plaintext signing key and is SHOW-ONCE: present on a
+ * create only, absent on every update, and never readable again. Lose it and
+ * the only recovery is `…/rotate-secret`.
+ */
+export interface WebhookUpsertResponse {
+    webhookId: string;
+    url: string;
+    events: WebhookEventType[];
+    active: boolean;
+    description?: string;
+    secret?: string;
+}
+/**
+ * `data` of `POST …/webhooks/{webhookId}/rotate-secret`. The request carries NO
+ * body — the path names the webhook.
+ *
+ * Mints a new signing key and returns it show-once. Only `updatedAt` moves
+ * with it (the response carries the value written); every other field is
+ * untouched.
+ */
+export interface WebhookRotateSecretResponse extends PublicWebhook {
+    secret: string;
+}
+/**
+ * `data` of `POST …/webhooks/{webhookId}/test`, answered `202`. The request
+ * carries NO body — the path names the webhook.
+ *
+ * Queues ONE signed {@link WebhookTestPayload}, never retried; the outcome is
+ * read off `…/deliveries`, on the {@link WebhookDelivery} row with this
+ * `deliveryId` and `test: true`.
+ */
+export interface WebhookTestResponse {
+    webhookId: string;
+    /**
+     * The queue's message id for the send. Optional because the handler
+     * forwards the SQS SDK's `MessageId` as-is and the SDK types it optional;
+     * a successful send carries one. Treat absent as "queued, id unknown".
+     */
+    deliveryId?: string;
+}
 /**
  * Payload for `payment.received` — a provider settlement landed and its
  * `PAYMENT#{storeId}` row is durable.

package/dist/whatsapp.d.ts

@@ -1,5 +1,6 @@
 /**
- * Published WhatsApp surface — the tenant-facing connection config only.
+ * Published WhatsApp surface — the tenant-facing connection config and the
+ * tenant's own template send (`POST /whatsapp/send`).
  *
  * ⚠️ **Meta's inbound webhook payload is NOT here and must not come back.**
  * The twelve shapes Meta POSTs to `/whatsapp` — the entry/change/value
@@ -49,5 +50,99 @@ declare global {
         /** ISO timestamp. */
         disconnectedAt?: string;
     }
+    /**
+     * Request body for `POST /whatsapp/send` — the TENANT's own template send,
+     * under `adminToken`, from the calling store's own connected number.
+     *
+     * ⚠️ The request must carry an `Idempotency-Key` header — without one it is
+     * refused `400 IDEMPOTENCY_KEY_REQUIRED`. Meta is called before anything is
+     * written, so a retried request with no key would send the message twice.
+     *
+     * ⚠️ There is no `storeId` member and there must never be one. The sending
+     * store is the authorizer's; a body-supplied one is the shape that would let
+     * a tenant address another tenant's number.
+     *
+     * ⚠️ Template only. Outside Meta's 24-hour customer-service window a free-form
+     * message is refused, and every case this serves (invoice reminder, payment
+     * link, order confirmation) is outside it — so there is no free-text member.
+     *
+     * Exactly one of `to` / `customerId` is required.
+     */
+    interface WhatsAppSendRequest {
+        /** Meta-approved template NAME, as registered against the store's own WhatsApp Business account. */
+        template: string;
+        /**
+         * Language code of the approved translation. Defaults to `'es'`.
+         *
+         * ⚠️ Meta matches a template by (name, language) PAIR — an approved template
+         * requested in the wrong language is refused exactly like one that was never
+         * approved (`WHATSAPP_TEMPLATE_NOT_APPROVED`).
+         */
+        languageCode?: string;
+        /**
+         * BODY placeholders, in `{{1}}`, `{{2}}`, … order.
+         *
+         * ⚠️ ORDER IS THE BINDING — Meta positions them, so an amount where a due
+         * date belongs is accepted, delivered and wrong.
+         */
+        parameters?: string[];
+        /** Recipient, digits with country code (`5491150123456`). Mutually exclusive with `customerId`. */
+        to?: string;
+        /** Recipient by id, resolved against the CALLING store's own customers. */
+        customerId?: string;
+        /** Display name for the message-log row only; never sent to Meta. */
+        name?: string;
+    }
+    /**
+     * `data` of a successful `POST /whatsapp/send`.
+     *
+     * (Named for the template send, not `WhatsAppSendResult`: that name belongs
+     * to the api-internal send seam and has a different shape.)
+     */
+    interface WhatsAppTemplateSendResult {
+        /** Meta's message id — the handle every later delivery-status webhook carries. */
+        messageId: string;
+        template: string;
+        /** ms epoch of the accepted send. */
+        sentAt: number;
+    }
 }
+/**
+ * `POST /whatsapp/send` refusals, beyond the cross-cutting `GATING_ERROR_CODES`
+ * (notably `PLAN_LIMIT_EXCEEDED` for the `whatsappMessages` monthly cap).
+ *
+ * - `VALIDATION_FAILED` · 400 — including a body naming both or neither of
+ *   `to` / `customerId`.
+ * - `IDEMPOTENCY_KEY_REQUIRED` · 400 — no `Idempotency-Key` header. The
+ *   idempotency wrapper's own codes (`INVALID_IDEMPOTENCY_KEY`,
+ *   `IDEMPOTENCY_KEY_REUSE`, `IDEMPOTENCY_IN_PROGRESS`, `IDEMPOTENCY_KEY_FAILED`,
+ *   `IDEMPOTENCY_LOCK_CONTENTION`) apply too. `IDEMPOTENCY_KEY_FAILED` (409)
+ *   means an earlier attempt under this key may have reached Meta: check the
+ *   recipient's chat before sending again under a NEW key.
+ * - `PLATFORM_INTEGRATION_DISABLED` · 503 — WhatsApp is switched off
+ *   platform-wide by SINFACTURA.
+ * - `WHATSAPP_NOT_CONNECTED` · 409 — the calling store has no connected
+ *   WhatsApp, or a connection with no stored token after a disconnect. Disable
+ *   the send control. ⚠️ Never falls back to the platform number.
+ * - `WHATSAPP_TOKEN_REJECTED` · 409 — connected, but Meta refused the stored
+ *   token. Reconnect.
+ * - `CUSTOMER_NOT_FOUND` · 404 / `WHATSAPP_RECIPIENT_PHONE_MISSING` · 400 — a bad
+ *   id versus a real customer with no usable number.
+ * - `WHATSAPP_RECIPIENT_NOT_ALLOWED` · 403 — non-production stages only: the
+ *   number is not on that stage's test allowlist. Nothing was sent.
+ * - `WHATSAPP_TEMPLATE_NOT_APPROVED` · 422 — not approved, paused, disabled,
+ *   wrong language or wrong parameter count (Meta does not tell these apart).
+ * - `WHATSAPP_RECIPIENT_OPTED_OUT` · 409 — the recipient cannot receive it.
+ * - `WHATSAPP_RATE_LIMITED` · 429 — throughput cap; retry later.
+ * - `WHATSAPP_ACCOUNT_SUSPENDED` · 403 — the WhatsApp Business account or the
+ *   number itself is restricted.
+ * - `WHATSAPP_SEND_FAILED` · 502 — any other Meta 4xx refusal; carries `metaCode`.
+ * - `WHATSAPP_SEND_UNCONFIRMED` · 502 — the request reached Meta and its outcome
+ *   is unknown: no answer came back, Meta answered 5xx, or Meta accepted it
+ *   without a message id.
+ *   The message may have been delivered, so the key is sealed:
+ *   a retry under it answers `IDEMPOTENCY_KEY_FAILED` rather than re-sending.
+ */
+export declare const WHATSAPP_SEND_ERROR_CODES: readonly ["VALIDATION_FAILED", "IDEMPOTENCY_KEY_REQUIRED", "PLATFORM_INTEGRATION_DISABLED", "WHATSAPP_NOT_CONNECTED", "WHATSAPP_TOKEN_REJECTED", "CUSTOMER_NOT_FOUND", "WHATSAPP_RECIPIENT_PHONE_MISSING", "WHATSAPP_RECIPIENT_NOT_ALLOWED", "WHATSAPP_TEMPLATE_NOT_APPROVED", "WHATSAPP_RECIPIENT_OPTED_OUT", "WHATSAPP_RATE_LIMITED", "WHATSAPP_ACCOUNT_SUSPENDED", "WHATSAPP_SEND_FAILED", "WHATSAPP_SEND_UNCONFIRMED"];
+export type WhatsAppSendErrorCode = (typeof WHATSAPP_SEND_ERROR_CODES)[number];
 export {};

package/dist/whatsapp.js

@@ -1,5 +1,6 @@
 /**
- * Published WhatsApp surface — the tenant-facing connection config only.
+ * Published WhatsApp surface — the tenant-facing connection config and the
+ * tenant's own template send (`POST /whatsapp/send`).
  *
  * ⚠️ **Meta's inbound webhook payload is NOT here and must not come back.**
  * The twelve shapes Meta POSTs to `/whatsapp` — the entry/change/value
@@ -12,4 +13,55 @@
  * `interface Document` made `document.filename` compile and type as `string`
  * against `lib.dom`'s `Document`, returning `undefined` at runtime.
  */
-export {};
+/**
+ * `POST /whatsapp/send` refusals, beyond the cross-cutting `GATING_ERROR_CODES`
+ * (notably `PLAN_LIMIT_EXCEEDED` for the `whatsappMessages` monthly cap).
+ *
+ * - `VALIDATION_FAILED` · 400 — including a body naming both or neither of
+ *   `to` / `customerId`.
+ * - `IDEMPOTENCY_KEY_REQUIRED` · 400 — no `Idempotency-Key` header. The
+ *   idempotency wrapper's own codes (`INVALID_IDEMPOTENCY_KEY`,
+ *   `IDEMPOTENCY_KEY_REUSE`, `IDEMPOTENCY_IN_PROGRESS`, `IDEMPOTENCY_KEY_FAILED`,
+ *   `IDEMPOTENCY_LOCK_CONTENTION`) apply too. `IDEMPOTENCY_KEY_FAILED` (409)
+ *   means an earlier attempt under this key may have reached Meta: check the
+ *   recipient's chat before sending again under a NEW key.
+ * - `PLATFORM_INTEGRATION_DISABLED` · 503 — WhatsApp is switched off
+ *   platform-wide by SINFACTURA.
+ * - `WHATSAPP_NOT_CONNECTED` · 409 — the calling store has no connected
+ *   WhatsApp, or a connection with no stored token after a disconnect. Disable
+ *   the send control. ⚠️ Never falls back to the platform number.
+ * - `WHATSAPP_TOKEN_REJECTED` · 409 — connected, but Meta refused the stored
+ *   token. Reconnect.
+ * - `CUSTOMER_NOT_FOUND` · 404 / `WHATSAPP_RECIPIENT_PHONE_MISSING` · 400 — a bad
+ *   id versus a real customer with no usable number.
+ * - `WHATSAPP_RECIPIENT_NOT_ALLOWED` · 403 — non-production stages only: the
+ *   number is not on that stage's test allowlist. Nothing was sent.
+ * - `WHATSAPP_TEMPLATE_NOT_APPROVED` · 422 — not approved, paused, disabled,
+ *   wrong language or wrong parameter count (Meta does not tell these apart).
+ * - `WHATSAPP_RECIPIENT_OPTED_OUT` · 409 — the recipient cannot receive it.
+ * - `WHATSAPP_RATE_LIMITED` · 429 — throughput cap; retry later.
+ * - `WHATSAPP_ACCOUNT_SUSPENDED` · 403 — the WhatsApp Business account or the
+ *   number itself is restricted.
+ * - `WHATSAPP_SEND_FAILED` · 502 — any other Meta 4xx refusal; carries `metaCode`.
+ * - `WHATSAPP_SEND_UNCONFIRMED` · 502 — the request reached Meta and its outcome
+ *   is unknown: no answer came back, Meta answered 5xx, or Meta accepted it
+ *   without a message id.
+ *   The message may have been delivered, so the key is sealed:
+ *   a retry under it answers `IDEMPOTENCY_KEY_FAILED` rather than re-sending.
+ */
+export const WHATSAPP_SEND_ERROR_CODES = [
+    'VALIDATION_FAILED',
+    'IDEMPOTENCY_KEY_REQUIRED',
+    'PLATFORM_INTEGRATION_DISABLED',
+    'WHATSAPP_NOT_CONNECTED',
+    'WHATSAPP_TOKEN_REJECTED',
+    'CUSTOMER_NOT_FOUND',
+    'WHATSAPP_RECIPIENT_PHONE_MISSING',
+    'WHATSAPP_RECIPIENT_NOT_ALLOWED',
+    'WHATSAPP_TEMPLATE_NOT_APPROVED',
+    'WHATSAPP_RECIPIENT_OPTED_OUT',
+    'WHATSAPP_RATE_LIMITED',
+    'WHATSAPP_ACCOUNT_SUSPENDED',
+    'WHATSAPP_SEND_FAILED',
+    'WHATSAPP_SEND_UNCONFIRMED',
+];

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "sinfactura-types",
-	"version": "1.10.449",
+	"version": "1.10.451",
 	"description": "Shared wire and entity contracts for the SINFACTURA platform.",
 	"type": "module",
 	"main": "dist/index.js",