Libraries tagged by wirecard

Create SSL wildcards domain certificates with own certificate authority for and ONLY for development.

Go to Download

Wordcards by Poodll — Composer/Packagist mirror of the Moodle plugin mod_wordcards, auto-updated from the Moodle plugins directory.

Go to Download

Extended Laravel Horizon providing listening dynamically added queues matched by wildcard.

Go to Download

Role and permission management for Laravel with a MongoDB backend

Go to Download

A highly optimized role and permission package for Laravel 11/12 with caching, multiple guards, wildcard permissions, super admin, and Laravel Gate integration

Go to Download

Flexible and polymorphic role & permission system for Laravel with time-based constraints, wildcard matching, and middleware integration.

Go to Download

Самый функциональный и быстрый PSR-14 диспетчер событий для PHP 8.1+: приоритеты, порядок before/after с топосортировкой, иерархия типов, именованные и wildcard-события, атрибуты, ленивые сервисы, отладочный и буферизующий диспетчеры, компиляция провайдера. Зависимости — только PSR.

Go to Download

A deploy bot for personal use.

Go to Download

A wrapper library of multiple free express tracking APIs in China.

Go to Download

Reads an array with dot-notation and asterix (wildcard).

Go to Download

phpClaw Cloud transport. Wildcard hook listener, payload builder, and HTTP client for the phpClaw Cloud service.

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

Route-based RBAC for Laravel with auto-synced permissions and wildcard support

Go to Download

Быстрый валидатор данных для PHP 8.1+: 20+ правил, точечная нотация и wildcard для вложенных полей, пользовательские правила и сообщения. Нулевые внешние зависимости.

Go to Download

Laravel IAM (Identity & Access Management) package with hierarchical permissions, wildcard support, and SaaS-ready design.

Go to Download