Introduction

Jelou API is a powerful tool that allows businesses to communicate with their customers in a more professional and efficient way, leading to better relationships and thriving commerce via chatbots.

This API enables users to build complex, interconnected systems and applications behind chatbots. By chatting through a human-like interface you can integrate and interact with the full Jelou platform, external services, libraries, systems, or other businesses. What is more, Jelou API is designed according to the REST principles as it is an API REST allowing different software applications to communicate with each other.

In practical terms, Jalou API allows chatbots to talk to other software, enabling them to work together, share information, and perform various tasks like customizing messages and keeping user context, or maintaining continuity by saving chat history, which is crucial for building modern and interconnected applications. Allowing an enhanced user experience and multi-turn conversations.

The API will always respond with an object, and according to the context, the resources can respond with a simple object or an array of objects.

This API accepts JSON request bodies and requires content to be content-type: application/JSON. This header must be specified in every request.

API version

The API's last version is the v1.2.

Domain

The Jelou API is available under the following domain:

The domain to call all the endpoints is https://api.jelou.ai

Errors

Jelou uses the HTTP standard to report errors. In general2XX indicates success, while 4XXindicates an error. In the event of a mistake, the response includes a JSON error object, with a codeand adescriptionwith more details. A5XXstatus shows that something happens on our side.

Code	Status	Description
bot_not_found	404	Bot is not assigned to your company
forbidden_bot	403	Bot is not allowed to be used by your company
message_could_not_be_send	400	Message failed to be send because of bad request
notification_could_not_be_send	400	Notification failed to be send because of bad request
unauthorized	401	Authorization is not allowed for this request
unprocessable_entity	422	Missing or bad field to process request
internal_server_error	500	Authorization company token doesn't have a company assigned

Rate Limits

The API can handle five requests per second.