Libraries tagged by IDIN
vocento/request-id
43989 Downloads
HTTP Request identifier to trace requests through microservices calls
userbase/client
8031 Downloads
UserBase PHP Client: Identity + Login + Signup Service
umutphp/wp-vulnerability-check
2839 Downloads
Check the WPScan Vulnerability Database via API to identify the security issues on plugins and WordPress installed.
typhoon/declaration-id
36458 Downloads
A set of identifiers for PHP declarations (constants, functions, classes, templates, etc.)
totten/php-symbol-diff
35647 Downloads
Identify changes in PHP code by symbol (class/method)
setono/client
14720 Downloads
PHP abstraction for identifying a browser client
ruark/laravel-inn
240 Downloads
Laravel package for INN Validation (Taxpayer identification number in Russia)
rowbot/punycode
198162 Downloads
A Bootstring encoding of Unicode for Internationalized Domain Names in Applications (IDNA).
pronovix/composer-logger
44218 Downloads
Simple PS3 compliant logger for Composer IOInterface.
plesk/wappspector
9433 Downloads
Command-line interface utility to analyze the file structure of a web hosting server and identify the frameworks and CMS used in the websites hosted on it.
php-extended/php-uri-parser-interface
197803 Downloads
A library to parse uniform resource identifiers (uri)
petrkotek/phpunit-naughtytestdetector
788922 Downloads
"Naughty test detector" for PHPUnit. Identifies tests, which don't clean after themselves.
peakhour-io/peakhour-api
16162 Downloads
Idiomatic PHP client for https://www.peakhour.io/api/explore/
paypaplane/svix-client
16674 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.
objective-php/matcher
128762 Downloads
Generic engine to match identifiers against simple yet powerful patterns