NexBotix Developer Documentation
Integrate WhatsApp automation, Website Chatbot widgets, custom In-House AI endpoints, transactional email delivery, Calendar booking, and Model Context Protocol (MCP) agents into any tech stack.
Base URL
https://nexbotix.online
Auth Header
X-API-Key: nex_...
Security
AES-256-GCM at rest
Protocols
REST + MCP Stream
Full Platform AI Agent Prompt
Universal SuiteCopy into Cursor, Windsurf, Claude Desktop, or Copilot for turnkey integration of all NexBotix services
You are helping me integrate with the NexBotix full-stack API platform.
## Environment Setup (do this first)
Add the following variable to your .env file:
NEXBOTIX_API_KEY=nex_your_key_here
Load in code:
- Node.js: process.env.NEXBOTIX_API_KEY
- Python: os.environ["NEXBOTIX_API_KEY"]
- Go: os.Getenv("NEXBOTIX_API_KEY")
Base URL: https://nexbotix.online
Header: X-API-Key: <value of NEXBOTIX_API_KEY> (keys start with nex_)
## Summary of Core APIs
1. WhatsApp Messaging: POST /api/v1/send (Single, Bulk Personalised with {{name}}, Scheduled)
2. Omnichannel Email: POST /api/v1/email/send (Transactional & Marketing HTML emails)
3. Website Chatbot & In-House AI: POST /api/website-chatbot/chat & webhook routing
4. MCP Server: POST /api/mcp (Streamable HTTP Model Context Protocol with 6 tools)
5. Calendar Booking: POST /api/calendar/public/:user/:slug/book (Google Meet links)
6. Marketing & SEO: POST /api/v1/quora/generate-answer, POST /api/v1/medium/generate-post, POST /api/seo/track
Please help me build a complete, resilient client wrapper for these services in my codebase.Authentication & API Key Management
How to authenticate all API requests to the NexBotix platform
All requests to NexBotix API endpoints must include your API Key in the X-API-Key HTTP header. Keys always begin with the nex_ prefix and can be generated from the dashboard.
# Required HTTP Header in all requests
X-API-Key: nex_live_991823019283019238
AES-256-GCM Encryption
All authentication tokens, third-party webhook headers, and SMTP credentials stored in NexBotix are encrypted at rest using industry-grade AES-256-GCM encryption.
Rate Limits & Quotas
API calls are rated per subscription tier. Bulk endpoints allow batching up to 50 recipients per single HTTP request for optimal throughput.
Standard HTTP Status Codes & Errors
Common status responses and troubleshooting steps
| Status | Meaning | Troubleshooting Guide |
|---|---|---|
| 200 OK / 202 Accepted | Request completed or queued for scheduling | Payload accepted; check job_id or response body. |
| 400 Bad Request | Invalid JSON structure or missing parameters | Verify phone format, recipient email, or max batch limits. |
| 401 Unauthorized | Missing or invalid API key | Ensure X-API-Key header starts with nex_. |
| 403 Forbidden | Subscription expired or domain not whitelisted | Verify plan status or whitelist domain in chatbot settings. |
| 503 Service Unavailable | WhatsApp session is disconnected or offline | Pair your WhatsApp session in the NexBotix Dashboard. |
Ready to build?
Generate your developer API key, copy the prompt into your AI agent or IDE, and integrate NexBotix services today.