Libraries tagged by Conservation
pixals/chatman
1 Downloads
Chatbot is a php library that uses machine learning to generate responses based on collection of known conversations.
owowagency/laravel-gossip
1127 Downloads
A package of conversation features for the Laravel framework.
open-functions/memory
1 Downloads
Memory OpenFunction provides a standardized API for storing, updating, retrieving, and removing conversational memories - empowering AI-powered applications with enhanced context management.
magecorebr/magento2-module-whatsapp-contact-button
151 Downloads
A Magento 2 module that adds a WhatsApp contact button to the storefront, enabling customers to initiate support conversations easily.
loffel/laravel-chatgpt
15 Downloads
Super simple wrapper for openai-php/client with error handling. Specifically for ChatGPT conversations.
lasmit/helpscoutreceipt
20 Downloads
A webhook to add receipt data to a note in new HelpScout conversations
jmbtechnologylimited/osmaths
1239 Downloads
conversations around the coordinate systems used for Ordnance Survey Open Data only
inzanty/perspectiveapi
1 Downloads
What if technology could help improve conversations online. Fork of original repository: stajor/perspectiveapi.
ierusalim/baseconvert
32 Downloads
Convertation from/to any user-defined base-chars-string throught decimal representation of arbitrary precision
filippo-toso/botman-dialogflow
149 Downloads
A Dialogflow middleware for Botman that calls the API only if the current user is not in a conversation drastically reducing the number of calls to Dialogflow (and their cost)
emiliopuljiz/api-whatsapp-business
11 Downloads
With this package you can create WhatsApp Business templates, start conversations through these templates. We are also going to have a panel to be able to receive and send messages with clients that we start conversations with.
dispositiontools/craft-persistiveutm
398 Downloads
Persist UTM values for tracking conversation rates
dczajkowski/colloquy
10 Downloads
A framework-agnostic package for managing persistent conversation contexts.
daphascomp/daphascompsms
2 Downloads
# Authentication Requests made to our APIs must be authenticated, there are two ways to do this: 1. Authenticating using your API apiUsername and apiPassword - `Basic Auth` 2. Authenticating using an Auth Token - `Bearer Token` ## Method 1: Basic Auth Basic Authentication is a method for an HTTP user agent (e.g., a web browser) to provide a apiUsername and apiPassword when making a request. When employing Basic Authentication, users include an encoded string in the Authorization header of each request they make. The string is used by the request’s recipient to verify users’ identity and rights to access a resource. The Authorization header follows this format: > Authorization: Basic base64(apiUsername:apiPassword) So if your apiUsername and apiPassword are `onfon` and `!@pas123`, the combination is `onfon:!@pas123`, and when base64 encoded, this becomes `b25mb246IUBwYXMxMjM=`. So requests made by this user would be sent with the following header: > Authorization: Basic b25mb246IUBwYXMxMjM= | Description | | ---------------------------------------------------------------------------------------------- | | **apiUsername** `String` `Required` Your onfon account apiUsername, retrieved from portal | | **apiPassword** `String` `Required` Your onfon account apiPassword, retrieved from portal | ## Method 2: Bearer Tokens This authentication stategy allows you to authenticate using JSON Web Token ``JWT` that will expire after given duration. Each Access Token is a `JWT`, an encoded JSON object with three parts: the `header`, the `payload`, and the `signature`. The following is an example Access Token generated for Conversations > Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c ### Getting the token To generate the token, make a `POST` request to `/v1/authorization` endpoint with your `apiUsername` and `apiPassword` This request should be made from your server and not on the client side such as browser or mobile environment. You will receive a JSON similar to below: `{ "token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c", "validDurationSeconds": 3600}` You can use the token received to make API calls. The token will be valid for value of `validDurationSeconds`, before which you should generate a new token. #### Request Body ``` { "apiUsername": "root", "apiPassword": "hakty11" } ``` #### Response Body ``` { "token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c", "validDurationSeconds": 3600 } ``` #### Example Curl ``` curl --location --request POST 'https://apis.onfonmedia.co.ke/v1/authorization' \ --data-raw '{ "apiUsername": "correctapiUsername", "apiPassword": "correctapiPassword" } ``` #### Making an API call You will be required to pass the token in `Authorization` header prefixed by `Bearer` when calling other endpoints. Example `Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c`
chat-php/chat
16 Downloads
Chat for internal system conversation.