Libraries tagged by user tracking

Go to Download

Example Magento 2 module showing how to use an interceptor to extend Block classes

Go to Download

common interfaces I use in an app. Mostly for teaching OOP

Go to Download

Lightweight, fast and easy to use classes for providing basic functionality for talking with remote api's including the REST standard.

Go to Download

A simple to use API-client in PHP for Cobinhood The World's First ZERO Trading Fees Cryptocurrency Exchange.

Go to Download

Use Laravel explicitly with or without trailing slashes, controlling URL generation and proper redirects for SEO.

Go to Download

PHP TradingBeep API is a PHP library for the TradingBeep.com API designed to be easy to use.

Go to Download

uses ebay API to access to search capabilities on the eBay platform

Go to Download

PHP Huobi.Pro API is an asynchronous PHP library for the Huobi API designed to be easy to use.

Go to Download

PHP BITMEX API is an asynchronous PHP library for the Bitmex API designed to be easy to use.

Go to Download

Example Magento 2 module showing how to use a mixin to overwrite Magento_Configurable

Go to Download

It is a training project used during education. Kurs https://www.youtube.com/playlist?list=PLKmH7u1gA9hoZfnMf-m3TFOmqhSn1wQs7

Go to Download

Library for use with Apigility training examples

Go to Download

this package use for Shaparak api, payment aggregator should use this package to talking with Shaparak webservice

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.40) is used. For example, calling `/info` is the same as calling `/v1.40/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 Base64 encoded (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