hexabot/api
2024-10-19 12:16:49 +01:00
..
assets feat: initial commit 2024-09-10 10:50:11 +01:00
migrations fix: attachment spelling issue 2024-10-13 08:27:28 +01:00
patches fix: database migrations through cli 2024-10-07 21:41:15 +01:00
src feat(api): automate adding copyright header 2024-10-19 12:16:49 +01:00
test fix: api docker container for mac users 2024-09-30 12:20:10 +01:00
.dockerignore fix: update readme and remove makefile 2024-10-02 17:01:55 +01:00
.eslintrc.js feat(api): automate adding copyright header 2024-10-19 12:16:49 +01:00
.gitignore fix: database migrations through hexabot-cli 2024-10-08 17:18:36 +01:00
.prettierrc feat: initial commit 2024-09-10 10:50:11 +01:00
.swcrc feat: initial commit 2024-09-10 10:50:11 +01:00
Dockerfile fix: api dockerfile for prod 2024-09-29 11:50:32 +01:00
merge-extensions-deps.js feat: initial commit 2024-09-10 10:50:11 +01:00
nest-cli.json feat: initial commit 2024-09-10 10:50:11 +01:00
package-lock.json fix: database migrations through cli 2024-10-07 21:41:15 +01:00
package.json fix(api): unit tests 2024-10-11 16:56:57 +01:00
README.md fix: database migrations through hexabot-cli 2024-10-08 17:18:36 +01:00
tsconfig.build.json feat: initial commit 2024-09-10 10:50:11 +01:00
tsconfig.doc.json feat: initial commit 2024-09-10 10:50:11 +01:00
tsconfig.json feat: initial commit 2024-09-10 10:50:11 +01:00

Hexabot API

Hexabot's API is a RESTful API built with NestJS, designed to handle requests from both the UI admin panel and various communication channels. The API powers core functionalities such as chatbot management, message flow, NLU (Natural Language Understanding), and plugin integrations.

Key Features

  • RESTful Architecture: Simple, standardized API architecture following REST principles.
  • Multi-Channel Support: Handles requests from different communication channels (e.g., web, mobile).
  • Modular Design: Organized into multiple modules for better scalability and maintainability.
  • Real-Time Communication: Integrates WebSocket support for real-time features.

API Modules

The API is divided into several key modules, each responsible for specific functionalities:

Core Modules

  • Analytics: Tracks and serves analytics data such as the number of messages exchanged and end-user retention statistics.
  • Attachment: Manages file uploads and downloads, enabling attachment handling across the chatbot.
  • Channel: Manages different communication channels through which the chatbot operates (e.g., web, mobile apps, etc.).
  • Chat: The core module for handling incoming channel requests and managing the chat flow as defined by the visual editor in the UI.
  • Knowledge Base: Content management module for defining content types, managing content, and configuring menus for chatbot interactions.
  • NLU: Manages NLU (Natural Language Understanding) entities such as intents, languages, and values used to detect and process user inputs intelligently.
  • Plugins: Manages extensions and plugins that integrate additional features and functionalities into the chatbot.
  • User: Manages user authentication, roles, and permissions, ensuring secure access to different parts of the system.
  • Extensions: A container for all types of extensions (channels, plugins, helpers) that can be added to expand the chatbot's functionality.
  • Settings: A module for management all types of settings that can be adjusted to customize the chatbot.

Utility Modules

  • WebSocket: Adds support for Websicket with Socket.IO, enabling real-time communication for events like live chat and user interactions.
  • Logger: Provides logging functionality to track and debug API requests and events.

Installation

$ npm install

Running the app in standalone

# development
$ npm run start

# watch mode
$ npm run start:dev

# production mode
$ npm run start:prod

Test

# unit tests
$ npm run test

# e2e tests
$ npm run test:e2e

# test coverage
$ npm run test:cov

Migrations

Hexabot includes a migrations feature to help manage database schema and data changes over time. Migrations allow you to apply or revert changes to the database in a consistent and controlled manner.

Creating a Migration

To create a new migration, use the following command from the root directory of Hexabot:

$ npx hexabot migrate create <migration-name>

Example:

$ npx hexabot migrate create all-users-language-fr

This command generates a new migration file in the /api/migrations folder. The file will look like this:

import getModels from '@/models/index';

export async function up(): Promise<void> {
  // Write migration here
}

export async function down(): Promise<void> {
  // Write migration here
}

Within the migration file, you can define the changes to be made in the up() function. For example, if you want to update the language field of all users to 'fr', your migration might look like this:

import getModels from '@/models/index';

export async function up(): Promise<void> {
  const { UserModel } = await getModels();
  await UserModel.updateMany({}, { language: 'fr' });
}

export async function down(): Promise<void> {}

Running Migrations Up

You can run the following command to run all pending migrations:

$ npx hexabot migrate up

Running Migrations Manually

If you want to run specific actions manually, you can get help by running the following command:

$ npx hexabot migrate help

Documentation

Access the Swagger API documentation by visiting the API url /docs once run it in development mode.

It's also possible to access the API reference documentation by running npm run doc.

For detailed information about the API routes and usage, refer to the API documentation or visit https://docs.hexabot.ai.

Contributing

We welcome contributions from the community! Whether you want to report a bug, suggest new features, or submit a pull request, your input is valuable to us.

Feel free to join us on Discord

License

This software is licensed under the GNU Affero General Public License v3.0 (AGPLv3) with the following additional terms:

  1. The name "Hexabot" is a trademark of Hexastack. You may not use this name in derivative works without express written permission.
  2. All derivative works must include clear attribution to the original creator and software, Hexastack and Hexabot, in a prominent location (e.g., in the software's "About" section, documentation, and README file).