Complete technical guide for integrating AISA with your applications
All API requests require an API key in the header:
Create a new AI chatbot from website URL
Get chatbot details and training status
Retrain chatbot with updated website content
Send message through AI chatbot
Get conversation history for a user
user_id
- User identifierlimit
- Number of messages (default: 50)offset
- Pagination offsetGet conversation analytics and metrics
start_date
- Start date (YYYY-MM-DD)end_date
- End date (YYYY-MM-DD)chatbot_id
- Specific chatbot (optional)Configure webhooks to receive real-time notifications about conversations and events.
message.received
Triggered when a user sends a message
conversation.started
Triggered when a new conversation begins
conversation.ended
Triggered when a conversation is marked as completed
lead.captured
Triggered when a potential lead is identified
For web applications and Node.js
For Python applications and AI/ML workflows
For PHP web applications
For Java and Android applications
The API uses standard HTTP status codes and returns detailed error messages in JSON format.
HTTP Status | Error Code | Description |
---|---|---|
400 | INVALID_REQUEST | Request body is malformed or missing required fields |
401 | INVALID_API_KEY | API key is invalid, expired, or missing |
403 | INSUFFICIENT_PERMISSIONS | API key doesn't have required permissions |
404 | RESOURCE_NOT_FOUND | Requested chatbot or resource doesn't exist |
429 | RATE_LIMIT_EXCEEDED | Too many requests, please slow down |
500 | INTERNAL_ERROR | Something went wrong on our end |
Rate limit information is included in response headers: