Libraries tagged by fits
flits/bik-sdk
1807 Downloads
An Bik-sdk for php project
fixsoftware/webpay-ws-php
22869 Downloads
GP Webpay WS API
fitbug/symfony-yaml-serializer-encoder-decoder
282926 Downloads
A encoder and decoder for Yaml for the Symfony Serializer Component.
fiskhandlarn/blade
4936 Downloads
A library for using Laravel Blade templates in WordPress/WordPlate.
fisharebest/php-polyfill
7295 Downloads
Polyfills for PHP 5.3 onwards
fisharebest/flysystem-chroot-adapter
33754 Downloads
Creates a filesystem from a sub-folder in another filesystem.
filsh/yii2-flags
7793 Downloads
Flags widget for yii2 framework
fiasco/symfony-console-style-markdown
120244 Downloads
A Symfony Console Style extension to support Markdown formatting.
fishpig/module-wordpress
36201 Downloads
Securely integrate WordPress and Magento 2.
wearerequired/translations-cache
1397 Downloads
Reduces file reads for translations by caching the first read via APCu.
typo3/cms-saltedpasswords
319272 Downloads
Uses a password hashing framework for storing passwords. Integrates into the system extension "felogin". Use SSL or rsaauth to secure datatransfer! Please read the manual first!
sbodak/magento2-checkout-custom-form
3298 Downloads
Add a custom form to Magento 2 checkout on the first step.
pmgw/payment-gateway-php-sdk
652 Downloads
BIG FISH Payment Gateway - PHP SDK
phpcfdi/csf-scraper
2101 Downloads
Obtiene los datos fiscales actuales de una persona moral o física dado su RFC y CIFID
paypaplane/svix-client
8669 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.