Libraries tagged by specifier
oliveris/text
5 Downloads
Sends text messages to a provider specified.
oliveris/sdk-mail
61 Downloads
Sends email and campaigns to a provider specified.
ofilin/yii2-geoip
14 Downloads
Yii 2 GeoIP extension. Returns country, city, lat, lng of current or specified IP (uses MaxMind's GeoIP2 databases)
ofelix03/transformer
19 Downloads
A simple associative (i.e. a key:value pair) data transformer which transforms the key's of an array data to some other specified keys. It also supports casting of data key's corresponding value to a specified PHP data type
nyco/wp-stat-collector
113 Downloads
A developer plugin for WordPress that adds hooks to enable the logging of data from the site to a specified MySQL database.
numerogeek/ebay-browse-api
2 Downloads
The Browse API has the following resources: item_summary: Lets shoppers search for specific items by keyword, GTIN, category, charity, product, image (Experimental Method), or item aspects and refine the results by using filters, such as aspects, compatibility, and fields values, or UI parameters. item: Lets you retrieve the details of a specific item or all the items in an item group, which is an item with variations such as color and size and check if a product is compatible with the specified item, such as if a specific car is compatible with a specific part. Provides a bridge between the eBay legacy APIs, such as Finding, and the RESTful APIs, which use different formats for the item IDs. The item_summary, search_by_image, and item resource calls require an Application access token.
nsantos/twig-sort-by-field
13 Downloads
A Twig Extension filter to sort an array of entries (objects or arrays) by the specified field
nogrod/ebay-sell-fulfillment-php-sdk
22 Downloads
Use the Fulfillment API to complete the process of packaging, addressing, handling, and shipping each order on behalf of the seller, in accordance with the payment method and timing specified at checkout.
nogrod/ebay-buy-browse-php-sdk
2 Downloads
The Browse API has the following resources:item_summary:Allows shoppers to search for specific items by keyword, GTIN, category, charity, product, image (Experimental Method), or item aspects and refine the results by using filters, such as aspects, compatibility, and fields values, or UI parameters.item:Allows shoppers to retrieve the details of a specific item or all items in an item group, which is an item with variations such as color and size and check if a product is compatible with the specified item, such as if a specific car is compatible with a specific part.This resource also provides a bridge between the eBay legacy APIs, such as the Finding, and the RESTful APIs, which use different formats for the item IDs.The item_summary, search_by_image, and item resource calls require an Application access token.
nobledsmarts/db-sentry
79 Downloads
Laravel Helper package for backing up Mysql database specified in env file and saving it to a folder
netsells/attribute-finder
1504 Downloads
A simple package that allows you to get all classes that have a given attribute in a specified directory
mralejandro/diff
10 Downloads
Generates diff between specified resources
mordilion/zf2-module-layouts
69 Downloads
ZF2ModuleLayouts is a simple module to build module specified layouts
milantex/mysql-tso
20 Downloads
Creates a PHP object which describes the MySQL table structure for a specified table in the database.
maxvaer/docker-openapi-php-client
4 Downloads
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..." } ```