LibraryH3lp APIs

Within LibraryH3lp, there are two primary APIs that you'll use when creating your own live chat apps. Our REST API allows you to query meta-data associated with your account. And you'll use XMPP for all things chat.

XMPP

At its heart, LibraryH3lp is an XMPP service. By building our product upon a widely-used and well-documented standard, we provide a predictable and robust live chat API upon which you can build your own chat applications. And, since there are a multitude of publicly available XMPP client libraries spanning just about any programming language you can think of, you have maximum flexibility when integrating LibraryH3lp into your own apps.

REST

The LibraryH3lp REST API allows you to query meta-data associated with your account, including chats, operators, queues, gateways, and widgets. You can also do some fancy things like determine the availability of queues and operators for chat, send files to guests, and e-mail transcripts. Since the API is based on REST principles, it's very easy to write and test your own chat applications. You can use your browser to access URLs, and use pretty much any HTTP client in any programming language to interact with our live chat API.

We have LibraryH3lp SDKs available for our REST API:

New to REST? From Wikipedia, "REST's client/server separation of concerns simplifies component implementation, reduces the complexity of connector semantics, improves the effectiveness of performance tuning, and increases the scalability of pure server components. Layered system constraints allow intermediaries-proxies, gateways, and firewalls-to be introduced at various points in the communication without changing the interfaces between components, thus allowing them to assist in communication translation or improve performance via large-scale, shared caching. REST enables intermediate processing by constraining messages to be self-descriptive: interaction is stateless between requests, standard methods and media types are used to indicate semantics and exchange information, and responses explicitly indicate cacheability."