Libraries tagged by Request client

Manage multiple REST servers to make requests in few lines and fluently.

Go to Download

This bundle allows to submit PubSub events via HTTP/POST requests to a Crossbar HTTP Publisher.

Go to Download

Guzzle plugin that allow you to forward headers from your current request into the the guzzle one automatically.

Go to Download

Utilities to help handle Micropub requests when building servers and clients

Go to Download

WURFL, the Wireless Universal Resource FiLe, is a Device Description Repository (DDR), i.e. a software component that maps HTTP Request headers to the profile of the HTTP client (Desktop, Mobile Device, Tablet, etc.) that issued the request

Go to Download

LLM client with support for cache, tools and async requests

Go to Download

# Introduction Welcome to the Passbase Verifications API docs. This documentation will help you understand our models and the Verification API with its endpoints. Based on this you can build your own system (i.e. verification) and hook it up to Passbase. In case of feedback or questions you can reach us under this email address: [[email protected]](mailto:[email protected]). A User submits a video selfie and valid identifying __Resources__ during a __Verification__ guided by the Passbase client-side integration. Once all the necessary __Resources__ are submitted, __Data points__ are extracted, digitized, and authenticated. These Data points then becomes part of the User's __Identity__. The User then consents to share __Resources__ and/or __Data points__ from their Identity with you. This information is passed to you and can be used to make decisions about a User (e.g. activate account). This table below explains our terminology further. | Term | Description | |-----------------------------------------|-------------| | [Identity](#tag/identity_model) | A set of Data points and Resources related to and owned by one single User. This data can be accessed by you through a Verification. | | Data points | Any data about a User extracted from a Resource (E.g. Passport Number, or Age). | | [Resource](#tag/resource_model) | A source document used to generate the Data points for a User (E.g. Passport). | | [User](#tag/user_model) | The owner of an email address associated with an Identity. | | Verification | A transaction through which a User consents to share Data points with you. If the Data points you request are not already available in the User's Identity, the Passbase client will ask the User to submit the necessary Resource required to extract them. | | Re-authentication (login) | A transaction through which a User can certify the ownership of Personal data previously shared through an Authentication. | # Authentication There are two forms of authentication for the API: • API Key • Bearer JWT Token

Go to Download

Log HTTP client requests and responses in Laravel

Go to Download

Contao 4/5 client hints request bundle.

Go to Download

A library that decorates the http client with request logging

Go to Download

A psr-18 compliant middleware client that handles requests through a psr-16 compliant simple-cache

Go to Download

A psr-18 compliant middleware client that handles requests through a psr-6 compliant cache.

Go to Download

A very basic Whois client for PHP. The library is limited in function since it's intended to be a low-level client that handles only request and raw output.

Go to Download

A psr-18 compliant middleware client that handles upgrade insecure request headers.

Go to Download

An http client that adds delays between requests for getting around time based bot detection

Go to Download