Libraries tagged by request signer

swop/github-webhook-stackphp

7 Favers
8 Downloads

Stack middleware which will verify if the incoming GitHub web hook request is correctly signed.

Go to Download


spinningcatstudios/lingara-apps

0 Favers
20 Downloads

The official Lingara app kit for PHP: verify, decode and answer Lingara's signed app requests with a card, through any PSR-15 stack.

Go to Download


coysh-digital/craft-manager-connector

0 Favers
68 Downloads

Reports operational metadata from a Craft CMS installation to a Manager platform over signed outbound requests, with one inbound endpoint whose only meaning is "check in now".

Go to Download


swop/stack-github-webhook

8 Favers
1000 Downloads

Stack middleware which will verify if the incoming GitHub web hook request is correctly signed.

Go to Download


mj-zana/security

0 Favers
24 Downloads

Password hashing, signed bearer tokens, request authentication and authorization by roles, permissions and policies for Zana applications

Go to Download


wpify/benefit-plus-gateway-sdk

0 Favers
253 Downloads

This is a "swagger" definition of application programming interface of the MΓΊzaPay by Benefit Plus e-commerce payment gateway. You may leverage this API from your e-shop to integrate payments by employee-benefits-programme funds. This version of the programme uses mobile payment application MΓΊzaPay. Requests signingAll requests except /auth/token must be signed by "SHA-256 with RSA" (RSASSA-PKCS1-v1_5, RFC 8017 chapter 8.2) electronic signatures. See online gateway documentation for details. ## Change log * v2 - 2025-06-26 * Added HEALTH value to productCode enum as mandated by the Czech state legislation. * amountAuthorized in PaymentStateResponse renamed to remainingAmount to better capture its meaining. * Added HTTP 410 Gone response to the cancelPayment() operation. * Corrected pattern of orderReferenceCode * Multiple corrections of the documentation, examples and field ordering changes - non-impacting.

Go to Download


macropage/sdk-ebay-rest-marketing

0 Favers
35 Downloads

The Marketing API offers two platforms that sellers can use to promote and advertise their products: Promoted Listings is an eBay ad service that lets sellers set up ad campaigns for the products they want to promote. eBay displays the ads in search results and in other marketing modules as SPONSORED listings. If an item in a Promoted Listings campaign sells, the seller is assessed a Promoted Listings fee, which is a seller-specified percentage applied to the sales price. For complete details, refer to the Promoted Listings playbook.Promotions Manager gives sellers a way to offer discounts on specific items as a way to attract buyers to their inventory. Sellers can set up discounts (such as "20% off" and other types of offers) on specific items or on an entire customer order. To further attract buyers, eBay prominently displays promotion teasers throughout buyer flows. For complete details, see Promotions Manager. Marketing reports, on both the Promoted Listings and Promotions Manager platforms, give sellers information that shows the effectiveness of their marketing strategies. The data gives sellers the ability to review and fine tune their marketing efforts.Store Email Campaign allows sellers to create and send email campaigns to customers who have signed up to receive their newsletter. For more information on email campaigns, see Store Email Campaigns.Important! Sellers must have an active eBay Store subscription, and they must accept the Terms and Conditions before they can make requests to these APIs in the Production environment. There are also site-specific listings requirements and restrictions associated with these marketing tools, as listed in the "requirements and restrictions" sections for Promoted Listings and Promotions Manager. The table below lists all the Marketing API calls grouped by resource.

Go to Download


factpulse/sdk

0 Favers
81 Downloads

REST API for electronic invoicing in France: Factur-X (CII), UBL 2.1, AFNOR PDP/PA, electronic signatures. ## 🎯 Main Features ### πŸ“„ Invoice Generation - **Formats**: CII XML, UBL 2.1 XML, or Factur-X PDF/A-3 - **Profiles** (CII/PDF): MINIMUM, BASIC, EN16931, EXTENDED - **UBL**: Always EN16931 compliant - **Standards**: EN 16931 (EU directive 2014/55), ISO 19005-3 (PDF/A-3), CII (UN/CEFACT), UBL 2.1 (OASIS) - **Simplified Format**: Generation from SIRET + auto-enrichment (Chorus Pro API + Business Search) ### βœ… Factur-X - Validation - **XML Validation**: Schematron (45 to 210+ rules depending on profile) - **PDF Validation**: PDF/A-3, Factur-X XMP metadata - **VeraPDF**: Strict PDF/A validation (146+ ISO 19005-3 rules) ### ✍️ Electronic Signature - **Standards**: PAdES-B-B, PAdES-B-T (RFC 3161 timestamping), PAdES-B-LT (long-term archival) - **eIDAS Levels**: SES (self-signed), AdES (commercial CA), QES (QTSP) - **Validation**: Cryptographic integrity and certificate verification ### πŸ“‹ Flux 6 - Invoice Lifecycle (CDAR) - **CDAR Messages**: Acknowledgements, invoice statuses - **PPF Statuses**: REFUSED (210), PAID (212) ### πŸ“Š Flux 10 - E-Reporting - **Tax Declarations**: International B2B, B2C - **Flow Types**: 10.1 (B2B transactions), 10.2 (B2B payments), 10.3 (B2C transactions), 10.4 (B2C payments) ### πŸ“‘ AFNOR PDP/PA (XP Z12-013) - **Flow Service**: Submit and search flows to PDPs - **Directory Service**: Company search (SIREN/SIRET) - **Multi-client**: Support for multiple PDP configs per user ### πŸ›οΈ Chorus Pro - **Public Sector Invoicing**: Complete API for Chorus Pro ### ⏳ Async Tasks - **Celery**: Asynchronous generation, validation and signing - **Polling**: Status tracking via `/tasks/{task_id}/status` - **Webhooks**: Automatic notifications when tasks complete ## πŸ”’ Authentication All requests require a **JWT token** in the Authorization header: ``` Authorization: Bearer YOUR_JWT_TOKEN ``` ### How to obtain a JWT token? #### πŸ”‘ Method 1: `/api/token/` API (Recommended) **URL:** `https://factpulse.fr/api/token/` This method is **recommended** for integration in your applications and CI/CD workflows. **Prerequisites:** Having set a password on your account **For users registered via email/password:** - You already have a password, use it directly **For users registered via OAuth (Google/GitHub):** - You must first set a password at: https://factpulse.fr/accounts/password/set/ - Once the password is created, you can use the API **Request example:** ```bash curl -X POST https://factpulse.fr/api/token/ \ -H "Content-Type: application/json" \ -d '{ "username": "[email protected]", "password": "your_password" }' ``` **Optional `client_uid` parameter:** To select credentials for a specific client (PA/PDP, Chorus Pro, signing certificates), add `client_uid`: ```bash curl -X POST https://factpulse.fr/api/token/ \ -H "Content-Type: application/json" \ -d '{ "username": "[email protected]", "password": "your_password", "client_uid": "550e8400-e29b-41d4-a716-446655440000" }' ``` The `client_uid` will be included in the JWT and allow the API to automatically use: - AFNOR/PDP credentials configured for this client - Chorus Pro credentials configured for this client - Electronic signature certificates configured for this client **Response:** ```json { "access": "eyJ0eXAiOiJKV1QiLCJhbGc...", // Access token (validity: 30 min) "refresh": "eyJ0eXAiOiJKV1QiLCJhbGc..." // Refresh token (validity: 7 days) } ``` **Advantages:** - βœ… Full automation (CI/CD, scripts) - βœ… Programmatic token management - βœ… Refresh token support for automatic access renewal - βœ… Easy integration in any language/tool #### πŸ–₯️ Method 2: Dashboard Generation (Alternative) **URL:** https://factpulse.fr/api/dashboard/ This method is suitable for quick tests or occasional use via the graphical interface. **How it works:** - Log in to the dashboard - Use the "Generate Test Token" or "Generate Production Token" buttons - Works for **all** users (OAuth and email/password), without requiring a password **Token types:** - **Test Token**: 24h validity, 1000 calls/day quota (free) - **Production Token**: 7 days validity, quota based on your plan **Advantages:** - βœ… Quick for API testing - βœ… No password required - βœ… Simple visual interface **Disadvantages:** - ❌ Requires manual action - ❌ No refresh token - ❌ Less suited for automation ### πŸ“š Full Documentation For more information on authentication and API usage: https://factpulse.fr/documentation-api/

Go to Download


spiderrobb/signed-request

3 Favers
37 Downloads

Simple Class for encoding and decoding SignedRequests that support a number of features and hash algorithms

Go to Download


simplon/signr

2 Favers
318 Downloads

Create and validate Signed Requests including data encryption.

Go to Download


dbd-net/signed-request

0 Favers
139 Downloads

Sign and validate HTTP requests

Go to Download


chatagency/laravel-signed-requests

0 Favers
24 Downloads

A package to (hopefully) make custom signed requests easier.

Go to Download


byfareska/hawk

0 Favers
27 Downloads

Hawk HTTP authentication (MAC-signed requests and bewit-signed URIs) for modern PHP β€” a maintained fork of dflydev/hawk

Go to Download


irfanokr/laravel-secure-bridge

0 Favers
0 Downloads

Signed, timestamped, replay-protected and optionally AES-256-GCM-encrypted request/response bridge between a JavaScript front-end (SPA or Blade + AJAX) and a Laravel API. Framework-agnostic JS client. Works on Laravel 5.5 through 12 and PHP 7.1+.

Go to Download


esigner/sdk

0 Favers
2 Downloads

Official PHP client for the esigner e-signing API: BankID, MitID and other eID signature requests, signed PDFs and verified webhooks.

Go to Download


<< Previous Next >>