Revokes and removes an access token from the web integration. External systems using this token will immediately lose access.
Integration identifier
Token identifier
Integration token deleted successfully
Web integration response including all configuration and metadata
Agent ID to associate with this web integration. The agent handles all conversations initiated through this integration.
1Integration name for identification purposes. Allowed characters: letters, numbers, hyphens, underscores, and spaces.
1 - 100^[a-zA-Z0-9\-_ ]+$Whether this integration is active. Disabled integrations cannot be used for new conversations.
Enabled features for this integration. Controls capabilities like web calls, chat, phone calls, and result delivery.
Widget appearance configuration including theme, position, colors, and custom styles for the embedded chat widget.
Unique integration identifier
1Organization ID that owns this integration
1Integration creation timestamp
Last modification timestamp
Access tokens associated with this integration. Tokens are used to authenticate websocket connections.
Description of the integration's purpose or usage context.
500Allowed origins for CORS security. Controls which websites can access this integration. If empty or null, all origins are allowed. Supported formats: "" (all origins), full HTTP/HTTPS URLs ("https://example.com", "http://localhost:3000"), wildcard subdomains (".example.com"), or domain names ("example.com"). Ports can only be specified in full URLs, not with domain names or wildcards.
Tool names that should be executed via websocket by the client. When the agent needs to use these tools during a conversation, it sends a websocketToolRequest message to the client, and the client must execute the tool and return the result via websocketToolResponse. If not specified, all tools are executed server-side.