Skip to content
This repository has been archived by the owner on Jun 27, 2024. It is now read-only.

Commit

Permalink
GITBOOK-1151: Omnichannel intro update
Browse files Browse the repository at this point in the history
  • Loading branch information
Faria1212 authored and gitbook-bot committed Nov 7, 2023
1 parent 75bddd1 commit 29b58e6
Show file tree
Hide file tree
Showing 11 changed files with 15 additions and 10 deletions.
18 changes: 9 additions & 9 deletions SUMMARY.md
Original file line number Diff line number Diff line change
Expand Up @@ -94,15 +94,15 @@
* [App Development Lifecycle](apps-engine/understanding-app-lifecycle.md)
* [App Configuration](apps-engine/app-configuration.md)
* [App Internationalization](apps-engine/app-internationalization.md)
* [Event Interfaces and Handlers](apps-engine/event-interfaces-and-handlers/README.md)
* [Email - Event Interfaces](apps-engine/event-interfaces-and-handlers/email-event-interfaces.md)
* [Livechat - Event Interfaces](apps-engine/event-interfaces-and-handlers/livechat-event-interfaces.md)
* [Message - Event Interfaces](apps-engine/event-interfaces-and-handlers/message-event-interfaces.md)
* [Room - Event Interfaces](apps-engine/event-interfaces-and-handlers/room-event-interfaces.md)
* [Settings - Event Interfaces](apps-engine/event-interfaces-and-handlers/settings-event-interfaces.md)
* [Uploads - Event Interfaces](apps-engine/event-interfaces-and-handlers/uploads-event-interfaces.md)
* [Users - Event Interfaces](apps-engine/event-interfaces-and-handlers/users-event-interfaces.md)
* [Examples](apps-engine/event-interfaces-and-handlers/examples.md)
* [Event Interfaces and Handlers](apps-engine/fundamentals-of-apps/event-interfaces.md)
* [Email - Event Interfaces](apps-engine/event-interfaces/email-event-interfaces.md)
* [Livechat - Event Interfaces](apps-engine/event-interfaces/livechat-event-interfaces.md)
* [Message - Event Interfaces](apps-engine/event-interfaces/message-event-interfaces.md)
* [Room - Event Interfaces](apps-engine/event-interfaces/room-event-interfaces.md)
* [Settings - Event Interfaces](apps-engine/event-interfaces/settings-event-interfaces.md)
* [Uploads - Event Interfaces](apps-engine/event-interfaces/uploads-event-interfaces.md)
* [Users - Event Interfaces](apps-engine/event-interfaces/users-event-interfaces.md)
* [Examples](apps-engine/event-interfaces/examples.md)
* [Apps-Engine User Interface](apps-engine/user-interface/README.md)
* [Opening the Contextual Bar](apps-engine/user-interface/uikit/opening-the-contextual-bar.md)
* [Building blocks](apps-engine/user-interface/uikit/building-blocks.md)
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -46,4 +46,4 @@ Here is an explanation of the handlers:

In the main class of your app, the class name extends `App`. This tells the Apps-Engine that `App` is the main class. To use events, the app must implement the event interfaces and this is done by using the keyword implements and the name of the events, comma separated.

In the following sections, you will find the event interfaces supported by Rocket.Chat. The event interfaces are grouped based on the events such as — email, livechat, messages, rooms, users, and so on. You will also find [examples](examples.md) of how these interfaces can be implemented.
In the following sections, you will find the event interfaces supported by Rocket.Chat. The event interfaces are grouped based on the events such as — email, livechat, messages, rooms, users, and so on. You will also find [examples](../event-interfaces/examples.md) of how these interfaces can be implemented.
5 changes: 5 additions & 0 deletions reference/api/rest-api/endpoints/omnichannel/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,11 @@

With the Rocket.Chat [Omnichannel](https://docs.rocket.chat/use-rocket.chat/omnichannel) feature, you can talk to your customers and website visitors, regardless of the channel they choose to connect with you.

The Omnichannel endpoints are of two types: authenticated and non-authenticated. 

* **Endpoints requiring authentication:** The workspace admins and managers use the endpoints that require authentication with a login method. 
* **Endpoints not requiring authentication:** Visitors can use the endpoints that require no authentication. These endpoints require a visitor `token` which is like an authentication parameter for visitors. Visitors can [register themselves](livechat-endpoints/visitor/register-a-new-livechat-visitor.md) by providing a random unique string as the `token` which can be used for other such endpoints. 

The endpoints in this section are:

<table data-card-size="large" data-view="cards"><thead><tr><th data-type="content-ref"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><a href="livechat-endpoints/">livechat-endpoints</a></td><td><a href="livechat-endpoints/">livechat-endpoints</a></td></tr><tr><td><a href="voice-channel-endpoints/">voice-channel-endpoints</a></td><td><a href="voice-channel-endpoints/">voice-channel-endpoints</a></td></tr><tr><td><a href="canned-responses/">canned-responses</a></td><td><a href="canned-responses/">canned-responses</a></td></tr></tbody></table>

0 comments on commit 29b58e6

Please sign in to comment.