Libraries tagged by retro

Retrieve Client IP from a ServerRequestInterface

Go to Download

A Laravel Nova Image Field with Flysystem Adapter for storing and retrieving media from Cloudinary

Go to Download

Traits & interfaces for utilizing cache mechanisms to store frequently retrieved data.

Go to Download

A library to calculate the time of next retry in apps that need to be fault tolerant and retry failed attempts of doing something.

Go to Download

Package for making Search/Retrieve via URL requests and parse the responses

Go to Download

This package simplifies working with Colombian holidays. It provides an easy, reliable, and convenient way to query, manipulate, or retrieve data related to holidays in Colombia, including detailed information about the reasons for each holiday.

Go to Download

Web scraper API with proxy rotation, retries, and with Chrome TLS fingerprint emulation

Go to Download

Converts SemVer version (like Composer packages) into integer version with operators. Helps managing versions: store, compare, sort and retrive by conditions.

Go to Download

Proxy list retrieve and provide

Go to Download

Utility package to retrieve Built for PS context and more

Go to Download

Retrieve all defined Models available in the Application or Vendor namespaces

Go to Download

Redis ODM (Object Document Mapper) for Symfony - store and retrieve PHP objects using Redis

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

An API for storing and retrieving static settings

Go to Download

Biblioteca com boletos e sistema de remessa e retorno para o Yii2 Framework

Go to Download