Libraries tagged by donation

donatorsky/php-xml-template-reader

2 Favers
2 Downloads

The PHP XML Reader where you show how to read the XML, and it does the rest for you.

Go to Download


donatorsky/enum

0 Favers
24 Downloads

Enumeration library for a PHP 7.1+

Go to Download


vkr/multimedia-analyzer-bundle

0 Favers
20 Downloads

A bundle for Symfony2/3 that analyzes multimedia file duration using GetID3

Go to Download


ultimadark/logger

0 Favers
17 Downloads

A class for logging timed durations when loading a page

Go to Download


stigwue/happrox

1 Favers
197 Downloads

Human approximation for numbers and durations.

Go to Download


ronnytorresmtz/route-measures

0 Favers
4 Downloads

A Laravel Nova field - Calculate the distance and duration of a route

Go to Download


mouf/utils.cache.session-cache

0 Favers
11 Downloads

This package contains a cache mechanism that relies on the session of the user. Therefore, the cache is a bit special, since it is kept for the duration of the session, and is only accessible by the current user. The session has to be started (using session_start()).

Go to Download


mecha-cms/x.panel.skin.construction

0 Favers
1 Downloads

Control panel skin with yellow color domination.

Go to Download


martenkoetsier/laravel-debugrequest

0 Favers
10 Downloads

Have a middleware log some details on every request such as route used, session, logged-in user, request parameters, and request duration.

Go to Download


kielabokkie/uber-cache

2 Favers
2 Downloads

Retrieve & store cache with a fallback for a specific duration

Go to Download


kanel/benchmark

0 Favers
17 Downloads

Benchmark your code by tracking duration and memory usage of your code

Go to Download


joanfabregat/iso8601-to-seconds

0 Favers
60 Downloads

Converts ISO 8601 duration to seconds

Go to Download


iarcadia/time

0 Favers
9 Downloads

A PHP time/duration library... again.

Go to Download


guilhermednt/buzz-proxied-curl-bundle

0 Favers
395 Downloads

Symfony DonatoHttpProxiedBuzzBundle

Go to Download


daphascomp/daphascompsms

0 Favers
1 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`

Go to Download


<< Previous Next >>