Libraries tagged by Push API

chencongbao/getui

0 Favers
0 Downloads

UniAPP个推SDK

Go to Download


wpoets/communication-handler

0 Favers
244 Downloads

Email, SMS and Push notification API Integration handler for Awesome enterprise

Go to Download


hatasever/onesignal

0 Favers
55 Downloads

Onesignal push Notification api

Go to Download


swaroop/apns2

1 Favers
27 Downloads

Simple & expressive PHP HTTP2 API for Apple Push Notification service (APNs) with comprehensive docs/constants.

Go to Download


ins0/php-pushover-sdk

0 Favers
7 Downloads

Pushover.net API SDK to send Push Messages

Go to Download


justinback/lago-php-client

0 Favers
13 Downloads

Lago API allows your application to push customer information and metrics (events) from your application to the billing application.

Go to Download


riftweb/firebase-notifications

0 Favers
0 Downloads

Effortlessly manage Firebase Cloud Messaging (FCM) notifications in your Laravel applications. This package simplifies sending FCM notifications with a clean and intuitive API, making it easy to integrate push notifications into your projects.

Go to Download


humamkerdiah/fcm-notifications

0 Favers
11 Downloads

A Laravel package for sending Firebase Cloud Messaging (FCM) push notifications with support for both legacy API and FCM HTTP v1 API. Features OAuth 2.0 authentication, batch processing, and comprehensive error handling.

Go to Download


vrakita/pushclient

0 Favers
1309 Downloads

Google Cloud Messaging Client API

Go to Download


sormagec/pusher-beam-laravel

0 Favers
223 Downloads

A Pusher Beams bridge for Laravel

Go to Download


sondt-1245/pusher-php-server

0 Favers
44 Downloads

Library for interacting with the Pusher REST API

Go to Download


quantomtech/laravel-firebase-batch-messaging

0 Favers
6 Downloads

Laravel package for batch Firebase cloud messaging API

Go to Download


pushey/pushey-php

0 Favers
16 Downloads

Library for interacting with the Pushey REST API

Go to Download


pushbots/pushbots-php

3 Favers
343 Downloads

PushBots PHP SDK

Go to Download


piurafunk/docker-php

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