@curviate/sdk 0.33.0 → 0.34.0

package/CHANGELOG.md

@@ -7,6 +7,24 @@ Versioning: semantic. Minor for additive changes, patch for bug fixes; no stabil
 
 ---
 
+## [0.34.0] - 2026-09-18
+
+Fixture and types regenerated against the deployed production document
+(`https://api.curviate.com`, 127 paths, server `dc4d3d9f0cce8159d7b6685a93291d71eec488c8`).
+
+### Fixed
+
+- **Ordinary-message subject retention copy corrected.** The served subject
+  description previously read "...The InMail subject line, when the platform
+  carries one on this message. Ordinary messages have none. ...", which a live
+  round-trip disproved: a classic `start_chat` to a FIRST_DEGREE contact, sent
+  with a subject, reads it back on `message.specifics.subject` and stores it
+  on both sides. The description now reads "The message's subject line, when
+  the platform carries one on this message. Typically an InMail opener, but an
+  ordinary message sent with a subject carries one too. ...". No type shape
+  change: description string only, at the three sites the served document
+  carries it.
+
 ## [0.33.0] - 2026-09-17
 
 The InMail subject on the message reads, now typed. Fixture and types

package/dist/index.d.ts

@@ -2922,7 +2922,7 @@ interface components {
             provider?: string;
             /** @description Platform-specific detail on the message. Carries `subject` for an InMail, which is set on the thread's opening message; absent or empty for an ordinary message. */
             specifics?: {
-                /** @description The InMail subject line, when the platform carries one on this message. Ordinary messages have none. Reading a conversation back stores the subject in your tenant's inbox records alongside the body, with no expiry. */
+                /** @description The message's subject line, when the platform carries one on this message. Typically an InMail opener, but an ordinary message sent with a subject carries one too. Reading a conversation back stores the subject in your tenant's inbox records alongside the body, with no expiry. */
                 subject?: string | null;
             };
             /** @description The sender's profile, when the platform returned one alongside the message. sender_id always carries the identifier; this object carries the rest of what is known about that person. */
@@ -11189,7 +11189,7 @@ interface operations {
                             provider?: string;
                             /** @description Platform-specific detail on the message. Carries `subject` for an InMail, which is set on the thread's opening message; absent or empty for an ordinary message. */
                             specifics?: {
-                                /** @description The InMail subject line, when the platform carries one on this message. Ordinary messages have none. Reading a conversation back stores the subject in your tenant's inbox records alongside the body, with no expiry. */
+                                /** @description The message's subject line, when the platform carries one on this message. Typically an InMail opener, but an ordinary message sent with a subject carries one too. Reading a conversation back stores the subject in your tenant's inbox records alongside the body, with no expiry. */
                                 subject?: string | null;
                             };
                             /** @description The sender's profile, when the platform returned one alongside the message. sender_id always carries the identifier; this object carries the rest of what is known about that person. */
@@ -11573,7 +11573,7 @@ interface operations {
                         provider?: string;
                         /** @description Platform-specific detail on the message. Carries `subject` for an InMail, which is set on the thread's opening message; absent or empty for an ordinary message. */
                         specifics?: {
-                            /** @description The InMail subject line, when the platform carries one on this message. Ordinary messages have none. Reading a conversation back stores the subject in your tenant's inbox records alongside the body, with no expiry. */
+                            /** @description The message's subject line, when the platform carries one on this message. Typically an InMail opener, but an ordinary message sent with a subject carries one too. Reading a conversation back stores the subject in your tenant's inbox records alongside the body, with no expiry. */
                             subject?: string | null;
                         };
                         /** @description The sender's profile, when the platform returned one alongside the message. sender_id always carries the identifier; this object carries the rest of what is known about that person. */
@@ -33664,7 +33664,7 @@ declare class CompaniesResource {
      * const result = await acc.companies.sendMessage("112013061", chats[0]!.id, {
      *   text: "Thanks for reaching out, happy to help!",
      * });
-     * console.log(result.sent_as); // { kind: "company", company_id: "112013061", name: "RedHire" }
+     * console.log(result.sent_as); // { kind: "company", company_id: "112013061", name: "Northwind Talent" }
      */
     sendMessage(identifier: string, chatId: string, body: CompanySendMessageBody): Promise<CompanySendMessageResult>;
 }

package/dist/index.js

@@ -2829,7 +2829,7 @@ var CompaniesResource = class {
    * const result = await acc.companies.sendMessage("112013061", chats[0]!.id, {
    *   text: "Thanks for reaching out, happy to help!",
    * });
-   * console.log(result.sent_as); // { kind: "company", company_id: "112013061", name: "RedHire" }
+   * console.log(result.sent_as); // { kind: "company", company_id: "112013061", name: "Northwind Talent" }
    */
   sendMessage(identifier, chatId, body) {
     return this.ctx.request({

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@curviate/sdk",
-  "version": "0.33.0",
+  "version": "0.34.0",
   "private": false,
   "description": "TypeScript SDK for the Curviate API.",
   "license": "MIT",

package/src/generated/types.ts

@@ -2825,7 +2825,7 @@ export interface components {
             provider?: string;
             /** @description Platform-specific detail on the message. Carries `subject` for an InMail, which is set on the thread's opening message; absent or empty for an ordinary message. */
             specifics?: {
-                /** @description The InMail subject line, when the platform carries one on this message. Ordinary messages have none. Reading a conversation back stores the subject in your tenant's inbox records alongside the body, with no expiry. */
+                /** @description The message's subject line, when the platform carries one on this message. Typically an InMail opener, but an ordinary message sent with a subject carries one too. Reading a conversation back stores the subject in your tenant's inbox records alongside the body, with no expiry. */
                 subject?: string | null;
             };
             /** @description The sender's profile, when the platform returned one alongside the message. sender_id always carries the identifier; this object carries the rest of what is known about that person. */
@@ -11093,7 +11093,7 @@ export interface operations {
                             provider?: string;
                             /** @description Platform-specific detail on the message. Carries `subject` for an InMail, which is set on the thread's opening message; absent or empty for an ordinary message. */
                             specifics?: {
-                                /** @description The InMail subject line, when the platform carries one on this message. Ordinary messages have none. Reading a conversation back stores the subject in your tenant's inbox records alongside the body, with no expiry. */
+                                /** @description The message's subject line, when the platform carries one on this message. Typically an InMail opener, but an ordinary message sent with a subject carries one too. Reading a conversation back stores the subject in your tenant's inbox records alongside the body, with no expiry. */
                                 subject?: string | null;
                             };
                             /** @description The sender's profile, when the platform returned one alongside the message. sender_id always carries the identifier; this object carries the rest of what is known about that person. */
@@ -11477,7 +11477,7 @@ export interface operations {
                         provider?: string;
                         /** @description Platform-specific detail on the message. Carries `subject` for an InMail, which is set on the thread's opening message; absent or empty for an ordinary message. */
                         specifics?: {
-                            /** @description The InMail subject line, when the platform carries one on this message. Ordinary messages have none. Reading a conversation back stores the subject in your tenant's inbox records alongside the body, with no expiry. */
+                            /** @description The message's subject line, when the platform carries one on this message. Typically an InMail opener, but an ordinary message sent with a subject carries one too. Reading a conversation back stores the subject in your tenant's inbox records alongside the body, with no expiry. */
                             subject?: string | null;
                         };
                         /** @description The sender's profile, when the platform returned one alongside the message. sender_id always carries the identifier; this object carries the rest of what is known about that person. */