Libraries tagged by Email Tracking

A lightweight, dependency-free PHP email library with SMTP, templating, queues, and analytics

Go to Download

Quick way to connect your php app with Omniva, a Baltic carrier serving Estonia, Latvia and Lithuania. Sends XML data via SOAP. Generates an Omniva order, outputs tracking number & orders package label via email to your email.

Go to Download

The Arta Public API provides quote generation, transport booking, and tracking capabilities. Additionally the API enables Arta partner organizations to configure email and webhook notifications for their accounts.

Go to Download

Esté paquete se encarga de administrar tus listas de correos electronicos y mandar campañas de mailings totalmente automatizadas. Es capaz de prover una API en las cuales se muestra información del traking de cada email enviado por este traker.

Go to Download

A library for interacting with the Royal Mail tracking service

Go to Download

E-mail Tracking Library on PHP

Go to Download

A library to ease development when working with the Royal Mail Tracking API

Go to Download

Basic Email Tasking helper

Go to Download

Royal Mail Tracking (for Server-side app) v2 REST API SDK generated from swagger specification

Go to Download

Add Matomo tracking server-side code to all requests in Roundcube

Go to Download

Prevent sending emails from non-production environments

Go to Download

A package sendmail with tracking

Go to Download

Add Piwik tracking server-side code to all requests in Roundcube

Go to Download

DPD Tracking (Portugal post office) tracking for PHP.

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