@proveanything/smartlinks 1.16.4 → 1.16.5

package/dist/api/proof.d.ts

@@ -187,6 +187,13 @@ export declare namespace proof {
      *   },
      * })
      * ```
+     * Direct to an SMS recipient by phone (E.164) and notify them by text:
+     * ```ts
+     * await proof.transfer(collectionId, productId, proofId, {
+     *   toPhone: '+14155551234',
+     *   comms: { recipient: { templateId: 'transfer-incoming', channel: 'sms' } },
+     * })
+     * ```
      */
     function transfer(collectionId: string, productId: string, proofId: string, options: TransferProofOptions): Promise<TransferProofResult>;
     /**

package/dist/api/proof.js

@@ -280,6 +280,13 @@ export var proof;
      *   },
      * })
      * ```
+     * Direct to an SMS recipient by phone (E.164) and notify them by text:
+     * ```ts
+     * await proof.transfer(collectionId, productId, proofId, {
+     *   toPhone: '+14155551234',
+     *   comms: { recipient: { templateId: 'transfer-incoming', channel: 'sms' } },
+     * })
+     * ```
      */
     async function transfer(collectionId, productId, proofId, options) {
         return post(transferBase(collectionId, productId, proofId), Object.assign({}, options));

package/dist/docs/API_SUMMARY.md

@@ -1,6 +1,6 @@
 # Smartlinks API Summary
 
-Version: 1.16.4  |  Generated: 2026-09-05T14:13:52.478Z
+Version: 1.16.5  |  Generated: 2026-09-05T15:46:49.017Z
 
 This is a concise summary of all available API functions and types.
 
@@ -7605,9 +7605,14 @@ interface CommsTrigger {
 ```typescript
 interface TransferProofOptions {
   * Comms to send. Roles: `recipient` (the named new owner) and `sender` (the
-  * initiator) for a directed transfer; `owner` for an open release.
+  * initiator) for a directed transfer; `owner` for an open release. For an
+  * SMS recipient, set `comms.recipient.channel = 'sms'`.
   comms?: CommsTriggerMap
   toEmail?: string
+  * Directed: recipient phone in E.164 (e.g. `+14155551234`). Resolves to the same
+  * user they log in as via SMS OTP (created if needed). Pair with an SMS comms
+  * trigger to notify them: `comms.recipient.channel = 'sms'`.
+  toPhone?: string
   toUserId?: string
   toName?: string
   release?: boolean
@@ -10470,7 +10475,7 @@ Redeem a grant token (anonymous or signed-in). Records the redemption and return
     productId: string,
     proofId: string,
     options: TransferProofOptions) → `Promise<TransferProofResult>`
-Start a push transfer of a proof (current owner / collection admin only). Directed — hand it to a named recipient who then calls {@link acceptTransfer}: ```ts await proof.transfer(collectionId, productId, proofId, { toEmail: 'buyer@example.com' }) ``` Open release — make the proof claimable by anyone: ```ts await proof.transfer(collectionId, productId, proofId, { release: true }) ``` Send comms by naming templates per role (server decides who receives each): ```ts await proof.transfer(collectionId, productId, proofId, { toEmail: 'buyer@example.com', comms: { recipient: { templateId: 'transfer-incoming', props: { note: 'Enjoy!' } }, sender:    { templateId: 'transfer-sent' }, }, }) ```
+Start a push transfer of a proof (current owner / collection admin only). Directed — hand it to a named recipient who then calls {@link acceptTransfer}: ```ts await proof.transfer(collectionId, productId, proofId, { toEmail: 'buyer@example.com' }) ``` Open release — make the proof claimable by anyone: ```ts await proof.transfer(collectionId, productId, proofId, { release: true }) ``` Send comms by naming templates per role (server decides who receives each): ```ts await proof.transfer(collectionId, productId, proofId, { toEmail: 'buyer@example.com', comms: { recipient: { templateId: 'transfer-incoming', props: { note: 'Enjoy!' } }, sender:    { templateId: 'transfer-sent' }, }, }) ``` Direct to an SMS recipient by phone (E.164) and notify them by text: ```ts await proof.transfer(collectionId, productId, proofId, { toPhone: '+14155551234', comms: { recipient: { templateId: 'transfer-incoming', channel: 'sms' } }, }) ```
 
 **acceptTransfer**(collectionId: string,
     productId: string,

package/dist/docs/proof-comms-triggers.md

@@ -128,6 +128,11 @@ Omit `comms` entirely and nothing is sent — comms are **opt-in**.
 
 - **Email-only recipients work.** A directed transfer to a `toEmail` that isn't a
   contact yet resolves/creates a contact before sending.
+- **SMS recipients work the same way.** A directed transfer to a `toPhone` (E.164)
+  resolves the recipient by phone and gives their contact a phone identity, so an
+  SMS-channel trigger (`channel: 'sms'`) reaches them. Because the phone maps to a
+  stable Firebase uid, they accept by logging in via SMS OTP — the accept is still
+  auth-gated exactly as with email.
 - **Consent + suppression apply.** Transactional sends still respect the contact's
   channel consent and suppression list; a template's `topic` governs this.
 - **Delivery is logged** to comms history (with your `appId` and a `ref`), so sends

package/dist/docs/proof-ownership-transfer.md

@@ -15,9 +15,20 @@ reserves states for them.
 
 | Mode | How | Who completes it |
 |------|-----|------------------|
-| **Directed** | Owner names a recipient (`toEmail` / `toUserId`). The proof is earmarked for them (`claimUserId`); you notify them with a comms trigger. | The named recipient calls `acceptTransfer`. |
+| **Directed** | Owner names a recipient (`toEmail` / `toPhone` / `toUserId`). The proof is earmarked for them (`claimUserId`); you notify them with a comms trigger. | The named recipient calls `acceptTransfer`. |
 | **Open release** | Owner marks the proof `claimable`. | Anyone claims it via the normal claim flow. |
 
+A `toPhone` recipient (E.164) resolves to the **same user they log in as via SMS
+OTP** — Firebase keys the uid by phone number, so the earmark matches when they
+sign in. Pair it with an SMS comms trigger to notify them by text:
+
+```ts
+await proof.transfer(collectionId, productId, proofId, {
+  toPhone: '+14155551234',
+  comms: { recipient: { templateId: 'transfer-incoming', channel: 'sms' } },
+})
+```
+
 Only the current owner (or a collection admin) can start a transfer. A proof can
 have **one active transfer at a time**.
 

package/dist/openapi.yaml

@@ -25882,6 +25882,8 @@ components:
           $ref: "#/components/schemas/CommsTriggerMap"
         toEmail:
           type: string
+        toPhone:
+          type: string
         toUserId:
           type: string
         toName:

package/dist/types/proof.d.ts

@@ -280,17 +280,24 @@ export interface CommsTrigger {
 export type CommsTriggerMap = Record<string, CommsTrigger>;
 /**
  * Start a push transfer. Provide **one** of:
- * - `toEmail` / `toUserId` — a directed transfer to a named recipient (they accept).
+ * - `toEmail` / `toPhone` / `toUserId` — a directed transfer to a named recipient (they accept).
  * - `release: true`        — an open release (the proof becomes claimable by anyone).
  */
 export interface TransferProofOptions {
     /**
      * Comms to send. Roles: `recipient` (the named new owner) and `sender` (the
-     * initiator) for a directed transfer; `owner` for an open release.
+     * initiator) for a directed transfer; `owner` for an open release. For an
+     * SMS recipient, set `comms.recipient.channel = 'sms'`.
      */
     comms?: CommsTriggerMap;
     /** Directed: recipient email (created/looked up if needed). */
     toEmail?: string;
+    /**
+     * Directed: recipient phone in E.164 (e.g. `+14155551234`). Resolves to the same
+     * user they log in as via SMS OTP (created if needed). Pair with an SMS comms
+     * trigger to notify them: `comms.recipient.channel = 'sms'`.
+     */
+    toPhone?: string;
     /** Directed: recipient user id, if already known. */
     toUserId?: string;
     /** Directed: display name for a newly-created recipient. */

package/docs/API_SUMMARY.md

@@ -1,6 +1,6 @@
 # Smartlinks API Summary
 
-Version: 1.16.4  |  Generated: 2026-09-05T14:13:52.478Z
+Version: 1.16.5  |  Generated: 2026-09-05T15:46:49.017Z
 
 This is a concise summary of all available API functions and types.
 
@@ -7605,9 +7605,14 @@ interface CommsTrigger {
 ```typescript
 interface TransferProofOptions {
   * Comms to send. Roles: `recipient` (the named new owner) and `sender` (the
-  * initiator) for a directed transfer; `owner` for an open release.
+  * initiator) for a directed transfer; `owner` for an open release. For an
+  * SMS recipient, set `comms.recipient.channel = 'sms'`.
   comms?: CommsTriggerMap
   toEmail?: string
+  * Directed: recipient phone in E.164 (e.g. `+14155551234`). Resolves to the same
+  * user they log in as via SMS OTP (created if needed). Pair with an SMS comms
+  * trigger to notify them: `comms.recipient.channel = 'sms'`.
+  toPhone?: string
   toUserId?: string
   toName?: string
   release?: boolean
@@ -10470,7 +10475,7 @@ Redeem a grant token (anonymous or signed-in). Records the redemption and return
     productId: string,
     proofId: string,
     options: TransferProofOptions) → `Promise<TransferProofResult>`
-Start a push transfer of a proof (current owner / collection admin only). Directed — hand it to a named recipient who then calls {@link acceptTransfer}: ```ts await proof.transfer(collectionId, productId, proofId, { toEmail: 'buyer@example.com' }) ``` Open release — make the proof claimable by anyone: ```ts await proof.transfer(collectionId, productId, proofId, { release: true }) ``` Send comms by naming templates per role (server decides who receives each): ```ts await proof.transfer(collectionId, productId, proofId, { toEmail: 'buyer@example.com', comms: { recipient: { templateId: 'transfer-incoming', props: { note: 'Enjoy!' } }, sender:    { templateId: 'transfer-sent' }, }, }) ```
+Start a push transfer of a proof (current owner / collection admin only). Directed — hand it to a named recipient who then calls {@link acceptTransfer}: ```ts await proof.transfer(collectionId, productId, proofId, { toEmail: 'buyer@example.com' }) ``` Open release — make the proof claimable by anyone: ```ts await proof.transfer(collectionId, productId, proofId, { release: true }) ``` Send comms by naming templates per role (server decides who receives each): ```ts await proof.transfer(collectionId, productId, proofId, { toEmail: 'buyer@example.com', comms: { recipient: { templateId: 'transfer-incoming', props: { note: 'Enjoy!' } }, sender:    { templateId: 'transfer-sent' }, }, }) ``` Direct to an SMS recipient by phone (E.164) and notify them by text: ```ts await proof.transfer(collectionId, productId, proofId, { toPhone: '+14155551234', comms: { recipient: { templateId: 'transfer-incoming', channel: 'sms' } }, }) ```
 
 **acceptTransfer**(collectionId: string,
     productId: string,

package/docs/proof-comms-triggers.md

@@ -128,6 +128,11 @@ Omit `comms` entirely and nothing is sent — comms are **opt-in**.
 
 - **Email-only recipients work.** A directed transfer to a `toEmail` that isn't a
   contact yet resolves/creates a contact before sending.
+- **SMS recipients work the same way.** A directed transfer to a `toPhone` (E.164)
+  resolves the recipient by phone and gives their contact a phone identity, so an
+  SMS-channel trigger (`channel: 'sms'`) reaches them. Because the phone maps to a
+  stable Firebase uid, they accept by logging in via SMS OTP — the accept is still
+  auth-gated exactly as with email.
 - **Consent + suppression apply.** Transactional sends still respect the contact's
   channel consent and suppression list; a template's `topic` governs this.
 - **Delivery is logged** to comms history (with your `appId` and a `ref`), so sends

package/docs/proof-ownership-transfer.md

@@ -15,9 +15,20 @@ reserves states for them.
 
 | Mode | How | Who completes it |
 |------|-----|------------------|
-| **Directed** | Owner names a recipient (`toEmail` / `toUserId`). The proof is earmarked for them (`claimUserId`); you notify them with a comms trigger. | The named recipient calls `acceptTransfer`. |
+| **Directed** | Owner names a recipient (`toEmail` / `toPhone` / `toUserId`). The proof is earmarked for them (`claimUserId`); you notify them with a comms trigger. | The named recipient calls `acceptTransfer`. |
 | **Open release** | Owner marks the proof `claimable`. | Anyone claims it via the normal claim flow. |
 
+A `toPhone` recipient (E.164) resolves to the **same user they log in as via SMS
+OTP** — Firebase keys the uid by phone number, so the earmark matches when they
+sign in. Pair it with an SMS comms trigger to notify them by text:
+
+```ts
+await proof.transfer(collectionId, productId, proofId, {
+  toPhone: '+14155551234',
+  comms: { recipient: { templateId: 'transfer-incoming', channel: 'sms' } },
+})
+```
+
 Only the current owner (or a collection admin) can start a transfer. A proof can
 have **one active transfer at a time**.
 

package/openapi.yaml

@@ -25882,6 +25882,8 @@ components:
           $ref: "#/components/schemas/CommsTriggerMap"
         toEmail:
           type: string
+        toPhone:
+          type: string
         toUserId:
           type: string
         toName:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@proveanything/smartlinks",
-  "version": "1.16.4",
+  "version": "1.16.5",
   "description": "Official JavaScript/TypeScript SDK for the Smartlinks API",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",