Quick choice
Pick the smallest integration that works.
Static or custom website
Difficulty: Medium
Generate an install key, paste one script tag, then test from the live domain.
Best when your team can edit the site code and approve the exact live domain.
<script src="https://venanto.com/static/widget.js" data-bot-id="BOT_ID" data-install-key="YOUR_INSTALL_KEY"></script>
WordPress
Difficulty: Easy
Install the plugin, click Connect Venanto in WordPress settings, sign in, and choose the assistant for the site.
Best when the customer has WordPress admin access and wants the fewest manual steps.
https://venanto.com/static/downloads/vilrio-chat.zip?v=0.2.6
Custom app or backend
Difficulty: Advanced
Keep the API key server-side and call `/api/v1/chat` from your own service.
Best when a developer owns auth, server calls, logging, and rollout testing.
Authorization: Bearer YOUR_VILRIO_KEY
We set it up for you
Difficulty: None for you
Hand it over with a setup request — FAQ cleanup, theme matching, hosting access, cPanel, SSH, or private system work.
Best when the customer needs launch help or the access path is not standard.
Console > Channels > Setup request
WordPress
Use the plugin when you want the fewest moving parts.
- Download `vilrio-chat.zip` from the console or `/static/downloads/vilrio-chat.zip?v=0.2.6`.
- Upload it in WordPress Plugins, then activate `Venanto Chat`.
- Open Settings > Venanto Chat and click `Connect Venanto`.
- Sign in to Venanto, choose the bot for this site, and return to WordPress.
- Choose title, accent color, suggestions, and whether the chat opens automatically.
- Send a test message on the live site and check install activity in Venanto.
Manual connection fields remain available inside the plugin only as an advanced fallback.
REST API
Backend chat uses the same bot, knowledge, tools, and audit history.
Prefer `Authorization: Bearer YOUR_VILRIO_KEY`. Existing server integrations can also send `X-Venanto-Api-Key: YOUR_VILRIO_KEY`. Create the narrowest key that fits the integration.
curl -X POST https://venanto.com/api/v1/chat \
-H "Authorization: Bearer YOUR_VILRIO_KEY" \
-H "Content-Type: application/json" \
-d '{
"bot_id": 123,
"message": "What are your hours?",
"external_user_ref": "customer-42"
}'
| Endpoint | Use it for |
| GET /api/v1/integration-guide | Machine-readable quickstart metadata. |
| GET /api/v1/bots | Find the bot IDs in the workspace. |
| POST /api/v1/install-keys | Create a limited custom website install key. |
| POST /api/v1/chat | Send backend-owned chat messages. |
| POST /api/v1/knowledge | Index text, FAQ, policy, or service content. |
| POST /api/v1/answer-test | Check which source sections answer a query before launch. |
Available API permissions cover bot lookup, install-key creation, chat, knowledge updates, and answer testing.
Knowledge
Index first, test answers second, then publish.
curl -X POST https://venanto.com/api/v1/knowledge \
-H "Authorization: Bearer YOUR_VILRIO_KEY" \
-H "Content-Type: application/json" \
-d '{
"bot_id": 123,
"title": "Service FAQ",
"content": "Emergency requests should be handed to staff immediately.",
"source_type": "api"
}'
curl -X POST https://venanto.com/api/v1/answer-test \
-H "Authorization: Bearer YOUR_VILRIO_KEY" \
-H "Content-Type: application/json" \
-d '{"bot_id":123,"query":"What happens in an emergency?"}'
Security boundary
Keep powerful credentials away from browsers.
Use API keys on servers only
Venanto API keys can list bots, chat, index knowledge, and create install keys. Do not ship them in JavaScript, WordPress, or mobile apps.
Use install keys for public surfaces
Install keys are limited to one bot and can be origin-locked, tracked, and revoked without rotating the account API key.
Setup help has a clear scope
Theme matching, knowledge preparation, hosting access, and custom CRM work are handled as a setup request with a defined scope and price up front.
Do not send secrets in setup forms
Use the forms for access method and non-secret context. Passwords, private credentials, and access codes need a separate secure handoff.