Libraries tagged by Safe PHP

Constraint for testing strings considering not-same line endings.

Go to Download

PHP Client for Genesis Payment Processing Gateway

Go to Download

Modern cookie management for PHP 7

Go to Download

Finally a sane way to register available commands and arguments and match your command line in PHP.

Go to Download

SharpAPI.com - AI-Powered Swiss Army Knife API. Save countless coding hours and supercharge your app with AI capabilities in just 2 lines of code.

Go to Download

A PHP library for easy image handling.

Go to Download

☯ Insightful PHP debugging assistant.

Go to Download

Strongly typed implementation of enumerable type in PHP which helps us to write a safer more readable code.

Go to Download

Global exception and errorhandling for TorneLIB, with all errorcodes stored in the same place.

Go to Download

Library files for Sage Starter Theme, forked by Lunar Build to support PHP8.1

Go to Download

PHP8 core functions that throw exceptions instead of returning FALSE on error

Go to Download

Consistent hashing "hashring" implementation in php (using the same algorithm as libketama)

Go to Download

Symfony bundle to integrate Stripe PHP SDK. Ability to save Stripe objects in database using Doctrine.

Go to Download

Symfony bundle to integrate Stripe PHP SDK. Ability to save Stripe objects in database using Doctrine.

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