SDKs

Official TypeScript and Python SDKs for the Weavz public API.

SDKs

Weavz provides hand-written SDKs for the customer-facing API surface. They wrap REST endpoints with resource-specific clients while preserving the same product primitives used in the dashboard and API reference.

SDKUse it for
TypeScript SDKNode.js and TypeScript backends, framework adapters, compile-time integration/action names, and generated action input types
Python SDKPython backends, agent frameworks, script-based workflows, and generated Pydantic action input validation

Generated Integration Catalog

Both SDKs include generated integration action input coverage from the same integration registry used by the API and docs.

NeedTypeScriptPythonRuntime API
List known integrationsintegrationNamesINTEGRATION_ACTIONS.keys()GET /api/v1/integrations
List actions for an integrationintegrationActions.slackget_action_names("slack")GET /api/v1/integrations?name=slack
Type or validate action inputActionInput<"slack", "send_channel_message">SlackSendChannelMessageInput or validate_action_input(...)Integration actions[*].props metadata
Resolve dynamic dropdownstyped client.integrations.resolveOptions(...)client.integrations.resolve_options(...)POST /api/v1/integrations/{name}/properties/options

Use the generated SDK helpers when the integration/action is known at build time. Use the runtime Integrations API when you are building dynamic catalogs, configuration UIs, or supporting integrations released after your SDK version.

Shared Naming Model

The SDKs use the same conceptual fields as the API:

ConceptREST / TypeScriptPython
Catalog integration slugintegrationNameintegration_name
Workspace integration create aliasaliasintegration_alias on workspace methods
Execution selector aliasintegrationAliasintegration_alias
Exact configured integration selectorworkspaceIntegrationIdworkspace_integration_id
Connection selectorconnectionExternalIdconnection_external_id
End-user selectorendUserIdend_user_id

Review Identifier Model and Integration Selectors before wiring multi-tenant or repeated-integration flows.