Skip to main content

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:


Download

ItemDetails
Plugin ZIP (v1.0.17)Download aventora-chatbot-1.0.17.zip
Install pathwp-content/plugins/aventora-chatbot/
RequiresWordPress 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

  1. In WordPress Admin, go to Plugins → Add New → Upload Plugin.
  2. Choose aventora-chatbot-1.0.17.zip and click Install Now.
  3. Activate the plugin.
  4. Open Settings → Aventora Chatbot and complete configuration (below).
  5. Enable Auto-inject widget in footer or add a shortcode to a page.

What you need from Aventora

Setting (WordPress)SourcePurpose
Tenant IDYour domain slug (lowercase)Must match Hub accounts.domain_name; passed as ?domain= on autoconnect
Domain API KeyAventora Admin → Settings → Domain API KeysServer-side chat token generation
Domain Chatbot API URLAventora (e.g. https://api-server.aventora.ai)Token API base URL; also used to auto-derive ?server= profile
Chatbot Base URLUsually https://ai.aventora.app (shared bot)Flutter chatbot iframe; tenant is not in the hostname
Chatbot Server ProfileOptional (ai, ca, tip, reable)Override when auto-detection from API URL is insufficient
Hub API KeyAccount-scoped key with call_managementCallback requests → Hub POST /start
Hub API URLAventora (default https://phone.aventora.ai)Engagement Hub base URL
Broker / admin phoneYour teamRequired 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 fieldNotes
Domain API KeyNever exposed to the browser; used only by /wp-json/aventora/v1/chatbot-token
Tenant IDLowercase slug, e.g. acme — passed as ?domain= on autoconnect
Chatbot Base URLDefault when empty: https://ai.aventora.app (shared multi-tenant bot)
Chatbot Server ProfileOptional override for ?server= (ai, ca, tip, reable); usually auto-detected from Domain Chatbot API URL
Widget position / theme / languageUI preferences
Auto-injectLoads 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 fieldNotes
Hub API KeyUse an account-scoped key with call_management; Account ID can stay empty
Account IDOnly if using an admin/proxy Hub key
Broker phoneE.164 format, e.g. +14161234567
Enable callback buttonFloating 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

ShortcodeDescription
[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

  1. The widget requests a token from WordPress REST (not from the browser with your API key).
  2. WordPress proxies to domain-chatbot and returns a short-lived token plus optional server profile (derived from your Domain Chatbot API URL).
  3. The widget loads {chatbot-url}/autoconnect?token=...&lang=...&server=...&domain=... (shared bot host, e.g. https://ai.aventora.app).
  4. Callback form submissions go to WordPress, then Hub POST /start with domain_name = Tenant ID.

Testing checklist

  1. Token endpointcurl -X POST https://yoursite.com/wp-json/aventora/v1/chatbot-token -H "Content-Type: application/json" -d "{\"domain\":\"acme\",\"language\":\"en\"}"200 with token and optional server.
  2. Config endpointcurl https://yoursite.com/wp-json/aventora/v1/configchatbotBaseUrl and optional server.
  3. Widget visible — bubble or embedded panel on the page.
  4. Chat — send a message; confirm in Domain Assistant → Logs in Admin.
  5. Callback — submit the callback form; confirm engagement in Hub call logs.
  6. Cache — exclude /wp-json/aventora/v1/chatbot-token from full-page cache (WP Rocket, etc.).

Use Clear All Caches on the plugin settings page after upgrades if assets look stale.


Troubleshooting

SymptomLikely causeFix
No widgetAuto-inject off and no shortcodeEnable auto-inject or add [aventora_chatbot]
Token 401/403Wrong Domain API KeyRegenerate in Admin; update settings
Token 500API URL or networkConfirm https://api.aventora.ai
Blank iframeWrong Chatbot Base URL or server profileUse https://ai.aventora.app; confirm server matches your API stack
Callback 400 domainWrong Tenant IDUse lowercase domain slug
Callback 403 domainHub account missing domain_chatbot_api_keyProvision key on Hub account
Callback 400 accountHub key not account-scopedUse account-bound key or set Account ID
Callback fails immediatelyMissing broker phoneSet 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

DateChange
2026-07-10v1.0.17 — shared bot host (ai.aventora.app), ?server= / ?domain= autoconnect, /config REST endpoint
2026-03v1.0.16 — Hub account-scoped keys, tenant slug normalization

Support