WordPress — Aventora Chatbot plugin
Install the official Aventora Chatbot plugin on WordPress to embed Domain Assistant (chat widget) and optional Engagement Hub callback requests (SMS/phone) without writing custom server code.
Audience: WordPress site owners, agencies, and integrators.
Related docs:
- Chatbot Embedding — how tokens and the widget work on any site
- Engagement Hub Start API — callback
/startpayload reference - Platform API Keys — domain vs Hub keys
Download
| Item | Details |
|---|---|
| Plugin ZIP (v1.0.17) | Download aventora-chatbot-1.0.17.zip |
| Install path | wp-content/plugins/aventora-chatbot/ |
| Requires | WordPress 5.0+, PHP 7.4+ |
The ZIP contains the full plugin (PHP, widget JS, admin settings, shortcodes, Gutenberg block). API keys are not included — configure them in WordPress after install.
Quick install
- In WordPress Admin, go to Plugins → Add New → Upload Plugin.
- Choose
aventora-chatbot-1.0.17.zipand click Install Now. - Activate the plugin.
- Open Settings → Aventora Chatbot and complete configuration (below).
- Enable Auto-inject widget in footer or add a shortcode to a page.
What you need from Aventora
| Setting (WordPress) | Source | Purpose |
|---|---|---|
| Tenant ID | Your domain slug (lowercase) | Must match Hub accounts.domain_name; passed as ?domain= on autoconnect |
| Domain API Key | Aventora Admin → Settings → Domain API Keys | Server-side chat token generation |
| Domain Chatbot API URL | Aventora (e.g. https://api-server.aventora.ai) | Token API base URL; also used to auto-derive ?server= profile |
| Chatbot Base URL | Usually https://ai.aventora.app (shared bot) | Flutter chatbot iframe; tenant is not in the hostname |
| Chatbot Server Profile | Optional (ai, ca, tip, reable) | Override when auto-detection from API URL is insufficient |
| Hub API Key | Account-scoped key with call_management | Callback requests → Hub POST /start |
| Hub API URL | Aventora (default https://phone.aventora.ai) | Engagement Hub base URL |
| Broker / admin phone | Your team | Required for conversational callbacks (user_phone_number) |
Registration: use Request API Key on the settings page, or aventora.ai/embedding/register.
For callbacks, Hub provisioning must include domain_chatbot_api_key on the account so Hub can validate domain_name on /start.
Settings reference
Chat widget (Domain Assistant)
| WordPress field | Notes |
|---|---|
| Domain API Key | Never exposed to the browser; used only by /wp-json/aventora/v1/chatbot-token |
| Tenant ID | Lowercase slug, e.g. acme — passed as ?domain= on autoconnect |
| Chatbot Base URL | Default when empty: https://ai.aventora.app (shared multi-tenant bot) |
| Chatbot Server Profile | Optional override for ?server= (ai, ca, tip, reable); usually auto-detected from Domain Chatbot API URL |
| Widget position / theme / language | UI preferences |
| Auto-inject | Loads widget on every page footer when enabled |
Demo mode: leave Domain API Key empty to try the widget with the shared aventora demo tenant (limited).
Callback button (Engagement Hub)
| WordPress field | Notes |
|---|---|
| Hub API Key | Use an account-scoped key with call_management; Account ID can stay empty |
| Account ID | Only if using an admin/proxy Hub key |
| Broker phone | E.164 format, e.g. +14161234567 |
| Enable callback button | Floating button + modal form |
Embedding options
Auto-inject (site-wide)
Settings → Aventora Chatbot → Auto-inject widget in footer — enables the floating chat bubble on all pages.
Shortcodes
| Shortcode | Description |
|---|---|
[aventora_chatbot] | Chat widget (inherits settings; supports position, theme, language, tenant, question, auto_open="true") |
[aventora_chatbot_button text="Chat with us" question="..."] | Button that opens the chatbot |
[aventora_callback_button] | Callback / contact request button |
[aventora_embed_website] | Website embed demo (iframe + overlay buttons) |
Examples:
[aventora_chatbot position="bottom-right" auto_open="true"]
[aventora_chatbot_button text="Ask a question" question="What are your hours?"]
[aventora_callback_button text="Request a callback"]
Gutenberg
Search for the Aventora Chatbot block in the block editor (same options as the shortcode).
Landing pages
Open chat from a custom button after the widget loads:
window.addEventListener('aventora:ready', function () {
window.AventoraChatbot.open();
});
Add ?open= to the page URL or auto_open="true" on the shortcode to open the widget automatically (useful for ad landing pages).
How it works
- The widget requests a token from WordPress REST (not from the browser with your API key).
- WordPress proxies to domain-chatbot and returns a short-lived token plus optional
serverprofile (derived from your Domain Chatbot API URL). - The widget loads
{chatbot-url}/autoconnect?token=...&lang=...&server=...&domain=...(shared bot host, e.g.https://ai.aventora.app). - Callback form submissions go to WordPress, then Hub
POST /startwithdomain_name= Tenant ID.
Testing checklist
- Token endpoint —
curl -X POST https://yoursite.com/wp-json/aventora/v1/chatbot-token -H "Content-Type: application/json" -d "{\"domain\":\"acme\",\"language\":\"en\"}"→200withtokenand optionalserver. - Config endpoint —
curl https://yoursite.com/wp-json/aventora/v1/config→chatbotBaseUrland optionalserver. - Widget visible — bubble or embedded panel on the page.
- Chat — send a message; confirm in Domain Assistant → Logs in Admin.
- Callback — submit the callback form; confirm engagement in Hub call logs.
- Cache — exclude
/wp-json/aventora/v1/chatbot-tokenfrom full-page cache (WP Rocket, etc.).
Use Clear All Caches on the plugin settings page after upgrades if assets look stale.
Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| No widget | Auto-inject off and no shortcode | Enable auto-inject or add [aventora_chatbot] |
| Token 401/403 | Wrong Domain API Key | Regenerate in Admin; update settings |
| Token 500 | API URL or network | Confirm https://api.aventora.ai |
| Blank iframe | Wrong Chatbot Base URL or server profile | Use https://ai.aventora.app; confirm server matches your API stack |
| Callback 400 domain | Wrong Tenant ID | Use lowercase domain slug |
| Callback 403 domain | Hub account missing domain_chatbot_api_key | Provision key on Hub account |
| Callback 400 account | Hub key not account-scoped | Use account-bound key or set Account ID |
| Callback fails immediately | Missing broker phone | Set Broker/Admin phone in settings |
Updates
When a new plugin version is published, download the latest ZIP from this page and install via Plugins → Add New → Upload Plugin. WordPress replaces the existing aventora-chatbot folder when the ZIP uses the same plugin directory name.
Changelog
| Date | Change |
|---|---|
| 2026-07-10 | v1.0.17 — shared bot host (ai.aventora.app), ?server= / ?domain= autoconnect, /config REST endpoint |
| 2026-03 | v1.0.16 — Hub account-scoped keys, tenant slug normalization |
Support
- Sales: sales@aventora.ai
- Website: aventora.ai