Libraries tagged by api email

nightstomp/kickbox-fork

0 Favers
4 Downloads

Official kickbox API library client for PHP

Go to Download


nholdren/marketing-cloud-php-soap

0 Favers
18 Downloads

PHP library for interacting with the Salesforce Marketing Cloud SOAP API

Go to Download


nasext/mandrill

2 Favers
49 Downloads

Mandrill API for Nette Framework

Go to Download


naroga/sendy-laravel

0 Favers
13 Downloads

Sendy API implementation for Laravel

Go to Download


mylittleparis/campaign-commander

4 Favers
2018 Downloads

Client for the Campaign Commander API (wrapper)

Go to Download


mozgbrasil/magento-base-php_72

0 Favers
51 Downloads

Módulo base para Magento

Go to Download


mozgbrasil/magento-base-php_71

0 Favers
147 Downloads

Módulo base para Magento

Go to Download


mozgbrasil/magento-base-php_56

0 Favers
1233 Downloads

Módulo base para Magento

Go to Download


mozgbrasil/magento-base-php_54

0 Favers
228 Downloads

Módulo base para Magento

Go to Download


mozgbrasil/magento-base-php56

0 Favers
963 Downloads

Módulo base para Magento

Go to Download


mozgbrasil/magento-base-php55

0 Favers
419 Downloads

Módulo base para Magento

Go to Download


mocean/mailchimp

1 Favers
1 Downloads

Mailchimp Integration with Mocean API

Go to Download


mfcc/mandrill

1 Favers
33 Downloads

Contact-Form using a honeypot for spam-protection and zendesk API for creating ticket

Go to Download


maxvaer/docker-openapi-php-client

0 Favers
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..." } ```

Go to Download


markix/markix-php

0 Favers
33 Downloads

PHP library for the Markix API.

Go to Download


<< Previous Next >>