Libraries tagged by plot
silverstripe/recipe-ccl
61488 Downloads
Silverstripe Cloud Platform CCL requirements recipe
silverstripe-terraformers/turnstile-captcha
4778 Downloads
Silverstripe CMS Turnstile Captcha Spam Protection Field
sendloop/mta-api-php
25599 Downloads
API client library for Sendloop MTA email as a service platform
seanhayes-com/laravel-hcaptcha
11139 Downloads
Client library for hCAPTCHA, a free service that protects websites from spam and abuse.
scribble/scribble
3680 Downloads
Publish your blog posts across multiple blogging platforms and sites
sanchescom/php-serial
768 Downloads
Multi-platform serial port access convenience class
rzani/zbar-qrdecoder
36090 Downloads
A PHP wrapper for Zbar. Decodes images/photos containing QR codes.
relewise/client
23852 Downloads
Relewise is a next generation personalization SaaS-platform, which offers functionality within product- and content recommendations and personalized search. This official SDK helps you interact with our API.
ramonztro/simple-scraper
6333 Downloads
SimpleScraper allows you to fetch Open Graph Protocol data, Twitter Card data and/or meta tags data.
pressbooks/excalibur
11309 Downloads
Excalibur is a SWORD protocol client for Pressbooks.
petrknap/optional
53303 Downloads
Optional (like in Java Platform SE 8 but in PHP)
pear/crypt_diffiehellman
10288 Downloads
Implementation of Diffie-Hellman Key Exchange cryptographic protocol for PHP5
payprocessing/phpsdk
56738 Downloads
Platron payment SDK
paypaplane/svix-client
15424 Downloads
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.
paragonie/libgossamer
148 Downloads
Library providing the Gossamer PKI protocol