Libraries tagged by usps api

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

UPS SOAP API Easy Tracking

Go to Download

The package is used to get access for remote feeds

Go to Download

API for Affiliate Tools

Go to Download

Traits that Bluora uses with their API wrappers.

Go to Download

Opayo PI (formerly SagePay PI) PHP API that uses PSR7, PSR17, PSR18 standards.

Go to Download

Allows for the uploading of documents in a Laravel application to a repository that uses the SWORD API

Go to Download

Simple base class for any API that uses bearer token authentication.

Go to Download

PhoneVerification component for IdP PW API that uses Nexmo services for SMS/Voice verification

Go to Download

Password store component for IdP PW API that uses Google as the backend.

Go to Download

Traits that Bluora uses with their API wrappers.

Go to Download

API client server that uses PHP encryption libraries.

Go to Download

This Package uses the general social media impressions API and makes it a Laravel package.

Go to Download

UPS PHP SDK based on OAuth

Go to Download

Uses screenshotapi.net to easily fetch screenshots from urls.

Go to Download