hexabot/api
2024-09-13 15:10:27 +01:00
..
assets feat: initial commit 2024-09-10 10:50:11 +01:00
migrations feat: initial commit 2024-09-10 10:50:11 +01:00
patches feat: initial commit 2024-09-10 10:50:11 +01:00
src fix: attachment upload 2024-09-13 15:10:27 +01:00
test feat: initial commit 2024-09-10 10:50:11 +01:00
.dockerignore feat: initial commit 2024-09-10 10:50:11 +01:00
.eslintrc.js feat: initial commit 2024-09-10 10:50:11 +01:00
.gitignore feat: initial commit 2024-09-10 10:50:11 +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 feat: initial commit 2024-09-10 10:50:11 +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 feat: initial commit 2024-09-10 10:50:11 +01:00
package.json feat: initial commit 2024-09-10 10:50:11 +01:00
README.md feat: initial commit 2024-09-10 10:50:11 +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, NLP (Natural Language Processing), 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.
  • CMS: Content management module for defining content types, managing content, and configuring menus for chatbot interactions.
  • NLP: Manages NLP 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

The API 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

You need to navigate to the api folder to run the following commands. To create a new migration, use the following command:

$ npm run create-migration <migration-name>

Example:

$ npm run create-migration all-users-language-fr

This command generates a new migration file in the ./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

All migrations are run automatically when the app starts.

Alternatively, you can run the following command in the root directory to run all pending migrations:

$ make migrate-up

Running Migrations Manually

If you want to run specific actions manually, you need to gain access to the api container and use the following command to run what you specifically want:

$ npm run migrate -h

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).
  3. SaaS Restriction: This software, or any derivative of it, may not be used to offer a competing product or service (SaaS) without prior written consent from Hexastack. Offering the software as a service or using it in a commercial cloud environment without express permission is strictly prohibited.