For developers and technical teams
Connect Smartwebchat to your stack.
Smartwebchat can sit on your website without becoming another isolated tool. Supported APIs, machine-readable specifications and event hooks let technical teams connect the customer assistant to existing workflows while keeping the product model focused.
REST API
Use approved API endpoints for supported product and agency operations. The API is designed for controlled integrations; Smartwebchat is not positioned as an unrestricted general-purpose agent platform.
OpenAPI
The available interface is described through an OpenAPI specification, giving developers a machine-readable source for operations, parameters and schemas.
MCP
Smartwebchat exposes approved capabilities through MCP so compatible AI systems and agents can discover and use the tools that are intentionally made available.
Webhooks
Use supported events to connect Smartwebchat with your own workflows and downstream systems. Event availability is defined by the technical source of truth.
Authentication and limits
Authentication, permissions and technical limits belong in the API reference. This page explains integration options without duplicating or drifting from the technical contract.
Agency workflows
Agencies can use supported interfaces as part of repeatable client setups. Multi-client and White Label rights still depend on the relevant plan and entitlements.
One technical reference
The API reference is maintained in English as the shared technical source. Local marketing pages explain the role of the interfaces; the contract itself stays in one place.
FAQ
Does Smartwebchat provide an SDK?
No public SDK is promised at launch. Use the documented REST API, OpenAPI specification, MCP interface and webhooks.
Can I integrate Smartwebchat into my own application?
Yes, when the required workflow is covered by the approved interfaces. Check the API reference for available operations and authentication.
Can AI agents discover Smartwebchat through MCP?
Smartwebchat provides an MCP interface for approved capabilities. The public tool set is centrally documented and intentionally limited.
Do I need the API to install the website assistant?
No. Standard website installation uses the supported website embed path. The developer interfaces are for deeper integrations and workflows.