Libraries tagged by signed

liberusoftware/webhooks

0 Favers
2146 Downloads

Signed filtered webhook endpoints, durable delivery attempts, retry, replay, and secret rotation.

Go to Download


konfig/snaptrade-php-sdk

1 Favers
26139 Downloads

Connect brokerage accounts to your app for live positions and trading. ## Rate limiting Two limits apply to requests signed with your `clientId`. The stricter one wins, and exceeding either returns `429 Too Many Requests`. - **Customer-level** — 250 requests/minute by default, scoped to your `clientId` and applied across all endpoints. Reported in `X-RateLimit-Limit`, `X-RateLimit-Remaining` and `X-RateLimit-Reset`. - **Account-level** — 10 requests/minute per account, scoped to (`clientId`, `accountId`). All covered operations for one account draw on the same bucket — reading balances and reading positions share it — and enforcement does not depend on the HTTP method, so updating an account consumes the same bucket as reading it. Only enforced for Personal users, and only for integrations it has been rolled out to — it is not yet in force for every Personal integration. It also does not apply on every operation that documents a 429 below. Where it applies it is reported in `X-RateLimit-Account-Limit`, `X-RateLimit-Account-Remaining` and `X-RateLimit-Account-Reset`. Do not read the absence of those headers as proof the limit is off — some configurations omit the rate limit headers while still enforcing the limit, so header absence tells you nothing about your allowance. On a 429, `X-RateLimit-Remaining: 0` means you hit the customer-level limit and `X-RateLimit-Account-Remaining: 0` means the account-level one. Wait for the corresponding `*-Reset` value (seconds) before retrying, or fall back to exponential backoff with jitter. Not every 429 is explained by those headers. A separate per-authenticated-user limit, reported in no `X-RateLimit-*` header, covers OAuth-authenticated requests and signed requests in configurations where the customer-level limit is not in effect — on the operations that use the default throttles. A few operations override those and are governed by the customer-level limit alone. The two do not stack: a signed request governed by the customer-level limit above is not additionally subject to the per-user one. If a 429 arrives with no header at zero — or with no `X-RateLimit-*` headers at all — honour `Retry-After` and back off. Treat the remaining counts as a hint, not a guarantee that the next request will succeed. Because the customer-level limit applies everywhere, any signed request can return 429. **OAuth-authenticated requests are an exception.** They are not subject to the customer-level limit and do not receive `X-RateLimit-Limit`, `X-RateLimit-Remaining` or `X-RateLimit-Reset` — do not wait on those headers or design around a customer-level allowance on this path. The account-level limit still applies to them on the account-data endpoints above, reported in the `X-RateLimit-Account-*` headers. On operations using the default throttles the per-user limit above applies to them as well, so an OAuth request can be rejected while the account headers still show capacity; on the few operations that override those throttles, OAuth callers have no per-user ceiling at all. Drive retries from `Retry-After` and exponential backoff with jitter rather than from the headers. See https://docs.snaptrade.com/docs/ratelimiting.

Go to Download


jardissupport/auth

0 Favers
990 Downloads

Signed access tokens and opaque refresh tokens with SQL token store and token authentication (subject + tenant), session handling, password hashing, and rights checks against token claims for PHP DDD applications — framework-free, no JWT, no third-party runtime dependencies beyond PHP built-ins and the Jardis contracts and dbquery packages

Go to Download


inly/core-web

0 Favers
1032 Downloads

Core snapshots, the Core API client, Core's signed pings, snapshot sitemaps, a chat relay, CDN media components and the Statamic connector API for Statamic websites fed by an Inly Core backoffice.

Go to Download


francodacosta/caparica

4 Favers
38210 Downloads

secure your REST api with signed requests

Go to Download


filippo-toso/p7m-extractor

5 Favers
21338 Downloads

A simple class that allows to extract the original file from a signed p7m file.

Go to Download


filagora/filagora-notifications

0 Favers
515 Downloads

Notification preferences for Filagora: per-person, per-category, per-channel choices, a category registry, suppression, signed unsubscribe, and bridges to push and forums.

Go to Download


dcodegroup/laravel-cloudfront-url-signer

0 Favers
42213 Downloads

Laravel 5.6+ wrapper around CloudFront canned signed URLs

Go to Download


contenir/contenir-preview-mezzio

0 Favers
1125 Downloads

Mezzio renderer for the Contenir preview protocol: answers the CMS's signed previews at /api/resource/preview by rendering the record's page with its unsaved values, and shared preview links at /preview/{id} behind a code.

Go to Download


cboxdk/license

0 Favers
2532 Downloads

Framework-agnostic, offline license core: mint and verify compact Ed25519-signed license artifacts (EdDSA JWTs) with entitlements, limits, deployment/domain binding, grace windows and signed revocation lists. The shared leaf both a billing issuer and a self-hosted verifier depend on.

Go to Download


nurtext/signed-request

1 Favers
7445 Downloads

Simple encoding/decoding of data and hash validation using a shared secret

Go to Download


leoralph/signed-url

0 Favers
821 Downloads

Enhanced signed URLs for Laravel, including attaching data, click limits and expiry.

Go to Download


akaunting/signed-url

10 Favers
14197 Downloads

Signed (unique) URL package for Laravel.

Go to Download


waiyanhein/lumen-signed-url

1 Favers
5948 Downloads

Package to generate temporary signd URL for Lumen framework

Go to Download


troisiemejoueur/cloudfront-signed-urls

0 Favers
3768 Downloads

Create AWS Cloudfront Signed Urls for S3 Craft CMS storage

Go to Download


<< Previous Next >>