SDKs

​

Install and make a call

npm install @talqing/sdk   # or: pip install talqing

import { TalqingClient } from "@talqing/sdk";

const talqing = new TalqingClient({
  baseUrl: "https://api.talqing.com",
  token: process.env.TALQING_API_KEY,
});

const agents = await talqing.agents.list({ limit: 50 });
console.log(agents.items.map((agent) => agent.config.name));

import os

from talqing import Talqing

with Talqing(token=os.environ["TALQING_API_KEY"], base_url="https://api.talqing.com") as talqing:
    agents = talqing.agents.list(limit=50)
    print([agent["config"]["name"] for agent in agents["items"]])

​

Conventions both clients share

• Same operations, same names. talqing.agents.versions.rollback is the same call in both. TypeScript spells namespaces in camelCase, Python in snake_case.
• Argument style. TypeScript takes one object: path and query parameters flat, the body keyed by its schema name ({ agent_id, createAgentRequest: {…} }). Python takes path parameters positionally and everything else as keyword arguments.
• The base URL is required and has no default; both clients refuse to start without it.
• One error type. Every non-2xx raises TalqingApiError (TypeScript) or TalqingAPIError (Python), carrying the API’s one error envelope. See errors.
• One paging helper, paginate, for every list endpoint. See pagination.
• Typed streams for the four event-stream methods: conversations.events and copilot.{agents,tools,tasks}.stream. See streaming.
• Types use the API’s names: AgentConfig, AgentResponse, CallOutcome, OperationRequest. TypeScript types; Python TypedDicts over plain dicts.

​

Resource namespaces