@naturali/sdk 0.47.1 → 0.48.0

package/dist/index.mjs

@@ -602,6 +602,272 @@ const createClient = (config = {}) => {
 const client = createClient(createConfig());
 //#endregion
 //#region src/generated/sdk.gen.ts
+var Channels = class {
+	/**
+	* List addresses
+	*/
+	static listAddresses(options) {
+		return (options.client ?? client).get({
+			url: "/v1/projects/{project_id}/addresses",
+			...options
+		});
+	}
+	/**
+	* Erase an address
+	*
+	* Removes the address, its conversations, and its runtime actor and sessions.
+	*
+	*/
+	static deleteAddress(options) {
+		return (options.client ?? client).delete({
+			url: "/v1/projects/{project_id}/addresses/{identifier}",
+			...options
+		});
+	}
+	/**
+	* Get an address
+	*/
+	static getAddress(options) {
+		return (options.client ?? client).get({
+			url: "/v1/projects/{project_id}/addresses/{identifier}",
+			...options
+		});
+	}
+	/**
+	* Set or clear this address's own action
+	*
+	* Upserts the address and its `action` in one call. `action: null` forgets the exception and defers back to the route table; any other `action` requires the same fields a route or channel default would (`agent_id` for `agent`, `text` for `message`).
+	*
+	*/
+	static setAddressAction(options) {
+		return (options.client ?? client).put({
+			url: "/v1/projects/{project_id}/addresses/{identifier}",
+			...options,
+			headers: {
+				"Content-Type": "application/json",
+				...options.headers
+			}
+		});
+	}
+	/**
+	* List an address's conversations
+	*
+	* Every conversation this address has had, across every channel it has ever messaged — an address is project-scoped, not channel-scoped.
+	*
+	*/
+	static listAddressConversations(options) {
+		return (options.client ?? client).get({
+			url: "/v1/projects/{project_id}/addresses/{identifier}/conversations",
+			...options
+		});
+	}
+	/**
+	* List channel kinds
+	*
+	* Every connectable kind, its surfaces, and the predicates its routes can match on (engine-wide ones like `address_known` plus its own, like Discord's `guild_id`).
+	*
+	*/
+	static listChannelKinds(options) {
+		return (options?.client ?? client).get({
+			url: "/v1/channel-kinds",
+			...options
+		});
+	}
+	/**
+	* List a channel's routes
+	*/
+	static listChannelRoutes(options) {
+		return (options.client ?? client).get({
+			url: "/v1/projects/{project_id}/channels/{channel_id}/routes",
+			...options
+		});
+	}
+	/**
+	* Create a route
+	*
+	* `action` is required; `agent_id` is required when it is `agent`, `text` when it is `message`; `repeat` is only valid alongside `action: message`. `surface`, when present, must be one this channel's kind serves (`GET /v1/channel-kinds`) — otherwise `400 unknown_surface`. `match` keys must be predicates that kind's registry declares — otherwise `400 unknown_predicate`. Writing a route for a surface whose transport mode is off (e.g. a Discord `guild_thread` route before `mention_threads` is enabled) still succeeds, with `unreachable_surface` in the response `warnings`.
+	*
+	*/
+	static createChannelRoute(options) {
+		return (options.client ?? client).post({
+			url: "/v1/projects/{project_id}/channels/{channel_id}/routes",
+			...options,
+			headers: {
+				"Content-Type": "application/json",
+				...options.headers
+			}
+		});
+	}
+	/**
+	* Delete a route
+	*/
+	static deleteChannelRoute(options) {
+		return (options.client ?? client).delete({
+			url: "/v1/projects/{project_id}/channels/{channel_id}/routes/{route_id}",
+			...options
+		});
+	}
+	/**
+	* Get a route
+	*/
+	static getChannelRoute(options) {
+		return (options.client ?? client).get({
+			url: "/v1/projects/{project_id}/channels/{channel_id}/routes/{route_id}",
+			...options
+		});
+	}
+	/**
+	* Replace a route
+	*
+	* Full replace, the same validation as create.
+	*/
+	static updateChannelRoute(options) {
+		return (options.client ?? client).patch({
+			url: "/v1/projects/{project_id}/channels/{channel_id}/routes/{route_id}",
+			...options,
+			headers: {
+				"Content-Type": "application/json",
+				...options.headers
+			}
+		});
+	}
+	/**
+	* Read the whole route table
+	*
+	* Every route across every channel in the project, one read — the table is small by construction (CHANNELS-ROUTING.md §3.6), so this is unpaginated.
+	*
+	*/
+	static listProjectChannelRoutes(options) {
+		return (options.client ?? client).get({
+			url: "/v1/projects/{project_id}/channel-routes",
+			...options
+		});
+	}
+	/**
+	* Open a conversation
+	*
+	* The outbound-first path (CHANNELS-ROUTING.md §3.11): open a conversation for `{ channel_id, identifier }` ahead of any inbound message, which falls out of making the identifier the unit rather than the message. Resolves the same three-layer action an inbound would (§3.6); a `409` when that does not land on an agent — there is nothing to open for a `message`/`silence` outcome.
+	*
+	*/
+	static createConversation(options) {
+		return (options.client ?? client).post({
+			url: "/v1/projects/{project_id}/conversations",
+			...options,
+			headers: {
+				"Content-Type": "application/json",
+				...options.headers
+			}
+		});
+	}
+	/**
+	* List channels
+	*
+	* Lists the channels connected in the project.
+	*/
+	static listChannels(options) {
+		return (options.client ?? client).get({
+			url: "/v1/projects/{project_id}/channels",
+			...options
+		});
+	}
+	/**
+	* Connect a channel
+	*
+	* Connect a channel. The required fields depend on `channel`; no credential is ever returned.
+	* **Discord** (`channel: discord`) — supply `application_id` and `bot_token`, plus the `modes` selecting which Gateway flows to serve (direct messages, and/or @mention-opens-a-thread). Returns `501` when the deployment has no `CHANNEL_TOKEN_KEY` configured.
+	* **WhatsApp** (default) — one of two credential paths, both filling the same write-only secret:
+	* * **BYOT** (`credential_source: byot`, default) — supply
+	* `phone_number_id` and `access_token` from your own Meta app.
+	*
+	* * **Embedded signup** (`credential_source: embedded_signup`) — supply
+	* `code` and `waba_id` (and optionally `pin`) from the Meta popup;
+	* naturali exchanges the `code` for the token and subscribes its app to
+	* the WABA, so the customer never hands over a token. Returns `501` on
+	* deployments where Meta App credentials are not configured.
+	*
+	*/
+	static createChannel(options) {
+		return (options.client ?? client).post({
+			url: "/v1/projects/{project_id}/channels",
+			...options,
+			headers: {
+				"Content-Type": "application/json",
+				...options.headers
+			}
+		});
+	}
+	/**
+	* Delete a channel
+	*
+	* Deletes the channel and whatever it provisioned — the WhatsApp send tool and write-only credential secret, or the Discord channel's sealed bot token (dropped with the row, closing its gateway connection).
+	*
+	*/
+	static deleteChannel(options) {
+		return (options.client ?? client).delete({
+			url: "/v1/projects/{project_id}/channels/{channel_id}",
+			...options
+		});
+	}
+	/**
+	* Get a channel
+	*/
+	static getChannel(options) {
+		return (options.client ?? client).get({
+			url: "/v1/projects/{project_id}/channels/{channel_id}",
+			...options
+		});
+	}
+	/**
+	* Update a channel
+	*
+	* Rotate the credential, update the kind's config (`waba_id` / `credential_source` for WhatsApp, `modes` for Discord), or flip the naturali-side status. At least one field is required. Rotating a WhatsApp token stores a new write-only secret, repoints the send tool and deletes the old secret; rotating a Discord bot token reseals it and the gateway worker reconnects with it.
+	*
+	*/
+	static updateChannel(options) {
+		return (options.client ?? client).patch({
+			url: "/v1/projects/{project_id}/channels/{channel_id}",
+			...options,
+			headers: {
+				"Content-Type": "application/json",
+				...options.headers
+			}
+		});
+	}
+	/**
+	* List the channel's conversations
+	*
+	* A cursor page of the channel's conversations, newest first. A conversation is one address's dialogue on the channel — the continuity anchor that resumes the same runtime session instead of starting fresh per message — so this is the read path for who has talked to the channel and which actor/session their dialogue resolved to.
+	* Conversations are created by the inbound path (the WhatsApp webhook, the Discord gateway worker) when a real message arrives; there is no way to create one directly.
+	*
+	*/
+	static listChannelConversations(options) {
+		return (options.client ?? client).get({
+			url: "/v1/projects/{project_id}/channels/{channel_id}/conversations",
+			...options
+		});
+	}
+	/**
+	* Get a conversation
+	*/
+	static getChannelConversation(options) {
+		return (options.client ?? client).get({
+			url: "/v1/projects/{project_id}/channels/{channel_id}/conversations/{conversation_id}",
+			...options
+		});
+	}
+	/**
+	* Read a conversation's transcript
+	*
+	* The conversation's messages, oldest first. naturali stores no message bodies — the dialogue lives in the runtime session the conversation maps to, so this reads through to the runtime. Pagination is `limit`/`offset` rather than an opaque cursor because the upstream is offset-based over a stable `position` ordering.
+	*
+	*/
+	static listChannelConversationMessages(options) {
+		return (options.client ?? client).get({
+			url: "/v1/projects/{project_id}/channels/{channel_id}/conversations/{conversation_id}/messages",
+			...options
+		});
+	}
+};
 var Agents = class {
 	/**
 	* List agents
@@ -950,150 +1216,6 @@ var Boards = class {
 		});
 	}
 };
-var Channels = class {
-	/**
-	* List channels
-	*
-	* Lists the channels connected in the project.
-	*/
-	static listChannels(options) {
-		return (options.client ?? client).get({
-			url: "/v1/projects/{project_id}/channels",
-			...options
-		});
-	}
-	/**
-	* Connect a channel
-	*
-	* Connect a channel. The required fields depend on `channel`; no credential is ever returned.
-	* **Discord** (`channel: discord`) — supply `application_id` and `bot_token`, plus the `modes` selecting which Gateway flows to serve (direct messages, and/or @mention-opens-a-thread). Returns `501` when the deployment has no `CHANNEL_TOKEN_KEY` configured.
-	* **WhatsApp** (default) — one of two credential paths, both filling the same write-only secret:
-	* * **BYOT** (`credential_source: byot`, default) — supply
-	* `phone_number_id` and `access_token` from your own Meta app.
-	*
-	* * **Embedded signup** (`credential_source: embedded_signup`) — supply
-	* `code` and `waba_id` (and optionally `pin`) from the Meta popup;
-	* naturali exchanges the `code` for the token and subscribes its app to
-	* the WABA, so the customer never hands over a token. Returns `501` on
-	* deployments where Meta App credentials are not configured.
-	*
-	*/
-	static createChannel(options) {
-		return (options.client ?? client).post({
-			url: "/v1/projects/{project_id}/channels",
-			...options,
-			headers: {
-				"Content-Type": "application/json",
-				...options.headers
-			}
-		});
-	}
-	/**
-	* Delete a channel
-	*
-	* Deletes the channel and whatever it provisioned — the WhatsApp send tool and write-only credential secret, or the Discord channel's sealed bot token (dropped with the row, closing its gateway connection).
-	*
-	*/
-	static deleteChannel(options) {
-		return (options.client ?? client).delete({
-			url: "/v1/projects/{project_id}/channels/{channel_id}",
-			...options
-		});
-	}
-	/**
-	* Get a channel
-	*/
-	static getChannel(options) {
-		return (options.client ?? client).get({
-			url: "/v1/projects/{project_id}/channels/{channel_id}",
-			...options
-		});
-	}
-	/**
-	* Update a channel
-	*
-	* Rotate the credential, update the kind's config (`waba_id` / `credential_source` for WhatsApp, `modes` for Discord), or flip the naturali-side status. At least one field is required. Rotating a WhatsApp token stores a new write-only secret, repoints the send tool and deletes the old secret; rotating a Discord bot token reseals it and the gateway worker reconnects with it.
-	*
-	*/
-	static updateChannel(options) {
-		return (options.client ?? client).patch({
-			url: "/v1/projects/{project_id}/channels/{channel_id}",
-			...options,
-			headers: {
-				"Content-Type": "application/json",
-				...options.headers
-			}
-		});
-	}
-	/**
-	* Unbind the channel
-	*/
-	static deleteChannelBinding(options) {
-		return (options.client ?? client).delete({
-			url: "/v1/projects/{project_id}/channels/{channel_id}/binding",
-			...options
-		});
-	}
-	/**
-	* Get the channel's binding
-	*/
-	static getChannelBinding(options) {
-		return (options.client ?? client).get({
-			url: "/v1/projects/{project_id}/channels/{channel_id}/binding",
-			...options
-		});
-	}
-	/**
-	* Set the channel's binding
-	*
-	* Create or replace the channel's agent binding (a channel has one binding in v1). `agent_id` is required and must be an agent owned in the project; `language` / `config` / `status` default to null / null / active when absent (full replace).
-	*
-	*/
-	static setChannelBinding(options) {
-		return (options.client ?? client).put({
-			url: "/v1/projects/{project_id}/channels/{channel_id}/binding",
-			...options,
-			headers: {
-				"Content-Type": "application/json",
-				...options.headers
-			}
-		});
-	}
-	/**
-	* List the channel's conversations
-	*
-	* A cursor page of the channel's conversations, newest first. A conversation is one address's dialogue on the channel — the continuity anchor that resumes the same runtime session instead of starting fresh per message — so this is the read path for who has talked to the channel and which actor/session their dialogue resolved to.
-	* Conversations are created by the inbound path (the WhatsApp webhook, the Discord gateway worker) when a real message arrives; there is no way to create one directly.
-	*
-	*/
-	static listChannelConversations(options) {
-		return (options.client ?? client).get({
-			url: "/v1/projects/{project_id}/channels/{channel_id}/conversations",
-			...options
-		});
-	}
-	/**
-	* Get a conversation
-	*/
-	static getChannelConversation(options) {
-		return (options.client ?? client).get({
-			url: "/v1/projects/{project_id}/channels/{channel_id}/conversations/{conversation_id}",
-			...options
-		});
-	}
-	/**
-	* Read a conversation's transcript
-	*
-	* The conversation's messages, oldest first. naturali stores no message bodies — the dialogue lives in the runtime session the conversation maps to, so this reads through to the runtime. Pagination is `limit`/`offset` rather than an opaque cursor because the upstream is offset-based over a stable `position` ordering.
-	*
-	*/
-	static listChannelConversationMessages(options) {
-		return (options.client ?? client).get({
-			url: "/v1/projects/{project_id}/channels/{channel_id}/conversations/{conversation_id}/messages",
-			...options
-		});
-	}
-};
 var Generations = class {
 	/**
 	* List an agent's generations

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@naturali/sdk",
-  "version": "0.47.1",
+  "version": "0.48.0",
   "description": "TypeScript SDK for the naturali.ai API, generated from its OpenAPI specs",
   "type": "module",
   "sideEffects": false,
@@ -37,7 +37,7 @@
     "tsx": "^4.23.1",
     "typescript": "~6.0.3",
     "vitest": "^4.1.10",
-    "@naturali/api": "0.47.1"
+    "@naturali/api": "0.48.0"
   },
   "scripts": {
     "generate": "tsx scripts/generate.ts",