Libraries tagged by sibs

PHP Service Bus (publish-subscribe pattern)

Go to Download

Cashbox provides an expressive, fluent interface to manage billing services.

Go to Download

Laravel Lightweight HTTP client

Go to Download

A tool to automatically fix phpDocumentor tags and annotations

Go to Download

Map widget encapsulating the OpenLayers 3 library for easy use in Yii 2.

Go to Download

Graphing and charting widget for Yii 2, based on Dygraphs.js

Go to Download

Yii2 Cashier provides an interface to Stripe's subscription billing services.

Go to Download

A more enjoyable local development experience for Windows Subsystem for Linux.

Go to Download

Google Noto CJK Substitute package for smaller package size

Go to Download

A simple observer pattern implementation based on symfony event handler, allowing you to subscribe and listen for various events that occur within your application.

Go to Download

FFMpeg video/audio/subs conversions, thumbnails, audio extraction, query...

Go to Download

A fast YAML parser that parses for the more commonly-used subset of YAML’s v1.0 and v1.2 specs.

Go to Download

Faster subsequent page-loads by prefetching in-viewport links during idle time

Go to Download

An OAuth2 plugin (subscriber) for Guzzle (forked from commerceguys/guzzle-oauth2-plugin)

Go to Download

Welcome to the Svix API documentation! Useful links: [Homepage](https://www.svix.com) | [Support email](mailto:[email protected]) | [Blog](https://www.svix.com/blog/) | [Slack Community](https://www.svix.com/slack/) # Introduction This is the reference documentation and schemas for the [Svix webhook service](https://www.svix.com) API. For tutorials and other documentation please refer to [the documentation](https://docs.svix.com). ## Main concepts In Svix you have four important entities you will be interacting with: - `messages`: these are the webhooks being sent. They can have contents and a few other properties. - `application`: this is where `messages` are sent to. Usually you want to create one application for each user on your platform. - `endpoint`: endpoints are the URLs messages will be sent to. Each application can have multiple `endpoints` and each message sent to that application will be sent to all of them (unless they are not subscribed to the sent event type). - `event-type`: event types are identifiers denoting the type of the message being sent. Event types are primarily used to decide which events are sent to which endpoint. ## Authentication Get your authentication token (`AUTH_TOKEN`) from the [Svix dashboard](https://dashboard.svix.com) and use it as part of the `Authorization` header as such: `Authorization: Bearer ${AUTH_TOKEN}`. For more information on authentication, please refer to the [authentication token docs](https://docs.svix.com/api-keys). ## Code samples The code samples assume you already have the respective libraries installed and you know how to use them. For the latest information on how to do that, please refer to [the documentation](https://docs.svix.com/). ## Idempotency Svix supports [idempotency](https://en.wikipedia.org/wiki/Idempotence) for safely retrying requests without accidentally performing the same operation twice. This is useful when an API call is disrupted in transit and you do not receive a response. To perform an idempotent request, pass the idempotency key in the `Idempotency-Key` header to the request. The idempotency key should be a unique value generated by the client. You can create the key in however way you like, though we suggest using UUID v4, or any other string with enough entropy to avoid collisions. Svix's idempotency works by saving the resulting status code and body of the first request made for any given idempotency key for any successful request. Subsequent requests with the same key return the same result. Please note that idempotency is only supported for `POST` requests. ## Cross-Origin Resource Sharing This API features Cross-Origin Resource Sharing (CORS) implemented in compliance with [W3C spec](https://www.w3.org/TR/cors/). And that allows cross-domain communication from the browser. All responses have a wildcard same-origin which makes them completely public and accessible to everyone, including any code on any site.

Go to Download