Libraries tagged by http verbs

Composer friendly version of http://web.archive.org/web/20130727034425/http://blog.kevburnsjr.com/php-unique-hash

Go to Download

Composer friendly version of http://web.archive.org/web/20130727034425/http://blog.kevburnsjr.com/php-unique-hash

Go to Download

PHP port of the Javascript version of LESS http://lesscss.org (Originally maintained by Josh Schmidt)

Go to Download

A brief overview of the API versions: v0: This version is solely for testing and does not interact with the database, nor does it involve any validation. It simply serves mock data. v1: This is the official version of the LtiSaas API, intended for production use. Please be informed that when testing version v0, the HTTP Access-Token header should be set with the value 'dummy'. Also, please note that the API has a limit of 2500 results per response. Additionally, all webservices support both POST and GET requests. However, the POST method is required when uploading files.

Go to Download

Package to check version according to Semantic Versioning 2.0.0 (http://semver.org).

Go to Download

DBVC: Database Version Control, inspired by http://dbv.vizuina.com/ and FlywayDB for Java.

Go to Download

Simply retrieve phone number informations by extracting them from the PHP version of Google handling library http://giggsey.com/libphonenumber/.

Go to Download

FPDF es una clase PHP que permite generar PDFs, está basada en la librería http://fpdf.org/ versión 1.8.1 créditos al mismo.

Go to Download

Fork of PHPRouter (http://miladrahimi.github.io/phprouter) version 2.3

Go to Download

PSR-0 compliant version of the Loggr PHP agent (http://github.com/loggr/loggr-php)

Go to Download

A less buggy fork of the original bootstrap slider found on http://www.eyecon.ro/ by Stefan Petre. It was forked so we could update the slider since the original wasn't under version control.

Go to Download

PHP Implementation of FCM HTTP v1 API. Fork from lkaybob/php-fcm-v1 and change Firebase JWT, Guzzle version

Go to Download

The Engine API is an HTTP API served by Docker Engine. It is the API the Docker client uses to communicate with the Engine, so everything the Docker client can do can be done with the API. Most of the client's commands map directly to API endpoints (e.g. `docker ps` is `GET /containers/json`). The notable exception is running containers, which consists of several API calls. # Errors The API uses standard HTTP status codes to indicate the success or failure of the API call. The body of the response will be JSON in the following format: ``` { "message": "page not found" } ``` # Versioning The API is usually changed in each release, so API calls are versioned to ensure that clients don't break. To lock to a specific version of the API, you prefix the URL with its version, for example, call `/v1.30/info` to use the v1.30 version of the `/info` endpoint. If the API version specified in the URL is not supported by the daemon, a HTTP `400 Bad Request` error message is returned. If you omit the version-prefix, the current version of the API (v1.44) is used. For example, calling `/info` is the same as calling `/v1.44/info`. Using the API without a version-prefix is deprecated and will be removed in a future release. Engine releases in the near future should support this version of the API, so your client will continue to work even if it is talking to a newer Engine. The API uses an open schema model, which means server may add extra properties to responses. Likewise, the server will ignore any extra query parameters and request body properties. When you write clients, you need to ignore additional properties in responses to ensure they do not break when talking to newer daemons. # Authentication Authentication for registries is handled client side. The client has to send authentication details to various endpoints that need to communicate with registries, such as `POST /images/(name)/push`. These are sent as `X-Registry-Auth` header as a [base64url encoded](https://tools.ietf.org/html/rfc4648#section-5) (JSON) string with the following structure: ``` { "username": "string", "password": "string", "email": "string", "serveraddress": "string" } ``` The `serveraddress` is a domain/IP without a protocol. Throughout this structure, double quotes are required. If you have already got an identity token from the [`/auth` endpoint](#operation/SystemAuth), you can just pass this instead of credentials: ``` { "identitytoken": "9cbaf023786cd7..." } ```

Go to Download

Data And Reporting product consists of API's which provides details of transaction and invoice informations about shell cards. The Shell Card Transaction and Invoice API is REST-based and employs Basic authentication in Version 1 and Oauth authentication in Version 2 end points. The API endpoints accept JSON-encoded request bodies, return JSON-encoded responses and use standard HTTP response codes. All resources are located in the Shell Card Platform. The Shell Card Platform is the overall platform that encompasses all the internal Shell systems used to manage resources.

Go to Download

PHP Pagination Class originaly from www.catchmyfame.com (http://www.catchmyfame.com/2014/02/06/php-pagination-class-version-3/)

Go to Download