Use the Video Live Streaming API to create and manage your RTMP live streams. This includes managing outputs as well as manually starting and stopping streams. See the [live streaming guide](https://cloudinary.com/documentation/video_live_streaming) for information on how to use the Live Streaming API to stream video to your users. **Note**: The Live Streaming API is currently in development and is available as a Public Beta, which means we value your feedback, so please feel free to [share any thoughts with us](https://support.cloudinary.com/hc/en-us/requests/new). The API supports Basic Authentication using your Cloudinary API Key and API Secret (which can be found on the Dashboard page of your [Cloudinary Console](https://console.cloudinary.com/pm)).

Go to Download

westwerk/contao-pageimage

0 Favers
64 Downloads

Controls for a static image and meta information on every page.

Go to Download

rafiki23/watermarkcredits

0 Favers
2 Downloads

WatermarkCredits is a Laravel package that enables the easy application of watermarks with logo and author information onto images.

Go to Download

ginsen/photosort

1 Favers
24 Downloads

A small app to rename or copy images files by Exif information of image

Go to Download

nicoverbruggen/mediaprobe

1 Favers
2 Downloads

MediaProbe leverages `ffprobe` and `ffmpeg` to extract info and cover images from MP3s or other media files.

Go to Download

coloredcow/books

0 Favers
11 Downloads

A way to find book info from a image

Go to Download

rollbackpt/url-extractor

3 Favers
140 Downloads

PHP Class to extract images and meta data information from URLs

Go to Download

esc-company/view-transformer

0 Favers
315 Downloads

View Transformer make profile image or name if client's information is empty.

Go to Download

basilicom-pimcore-plugin/iptc-import

0 Favers
9 Downloads

Upload images and auto create meta information based on iptc data.

Go to Download

buse974/simple-page-crawler

1 Favers
1567 Downloads

ZF3 module v0.3.0 - Provide a crawler to get web page informations : title, meta, heading tags and images

Go to Download

piurafunk/docker-php

0 Favers
8 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

<< Previous Next >>