Libraries tagged by connect api

Laravel integration for Lock: sign users in, handle back-channel logout and obtain API tokens

Go to Download

Seamlessly connect Laravel to Google Drive with a Flysystem v3 adapter and Gdrive helper — upload, list, and manage your Drive files effortlessly.

Go to Download

A powerful MCP server inspector and documentation UI for Laravel — tools reference, interactive playground, scope explorer, and client connect guides.

Go to Download

The keyclock plugin provides a simple way to integrate Keycloak admin api with full support for Laravel framework.

Go to Download

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

A small, lightweight utility to perform curl calls using GET, POST, PUT, PACTH, DELETE, HEAD, TRACE, OPTIONS methods...

Go to Download

Connect any printer to your application with PrintNode Client and easy to use JSON API

Go to Download

Customize JWT claims in Laravel Passport access tokens

Go to Download

A typed community PHP SDK for the WEBFLEET.connect API

Go to Download

PHP package to connect your application to Pasargad Internet Payment Gateway through RESTful API

Go to Download

PHP library for malware scanning and cleanup using Imunify Connect API

Go to Download

Php Sdk to connect with Api Fuel

Go to Download

PHP Teamleader oauth2 package to connect with Teamleader API (https://developer.teamleader.eu/)

Go to Download

A Statamic addon to connect with Notion API

Go to Download

CloudABIS™ can compare millions of ISO fingerprint templates/sec for fast 1:N matching & de-duplication requirements. Customers simply connect through our API or CloudApper™ software & instantly have the ability to perform fast 1:N matching. Our software supports many fingerprint readers & device activation is seamless with our CloudScanr™ app. CloudScanr™ also enables the biometric system to instantly work across any web browser.

Go to Download