Libraries tagged by Poster API

API to store posts from WordPress to Elasticsearch and back.

Go to Download

This is post Helper for access API from jsonplaceholder.typicode.com

Go to Download

Generic but customisable post endpoint to expose post content via WP-API

Go to Download

Generic but customisable post endpoint to expose post content via WP-API

Go to Download

Expose Post Formats in WP REST API.

Go to Download

This module extends the Webform module's Remote Post Webform Handler plugin to make remote posts asynchronous using Drupal Queue API.

Go to Download

PHP API Client for Multi-Post

Go to Download

Cybersource checkout API for Silent Order POST (POST)PHP

Go to Download

An API client for Ricoh Click & Post service

Go to Download

Use the Facebook SDK via batch requests without having to complexify the code with the pre-processing and post-processing phases.

Go to Download

Package generated from https://mojezasielky.posta.sk/integration/webServices/api?wsdl using wsdltophp/packagegenerator

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

Simple implementation which alows user to post texts to Telegram channels or groups using Telegram Bot API

Go to Download

This plugin brings over data from social sites like Facebook and Twitter viatheir APIs and syncs them with a custom post type available for your theme.

Go to Download

Сервис пользовательских постов

Go to Download