Libraries tagged by api consumer

lde/api-helper

5 Favers
15235 Downloads

Laravel package to help consume REST and XML APIs with little effort.

Go to Download


agentcat/api

0 Favers
689 Downloads

Typed request models for the AgentCat public API, generated from its OpenAPI schema and consumed by agentcat/sdk.

Go to Download


gabrielkaputa/bitly

4 Favers
76567 Downloads

PHP library to consume bit.ly API

Go to Download


tomloprod/ionic-push-php

23 Favers
6662 Downloads

ionic-push-php is a library that allows you to consume the Ionic Cloud API for sending push notifications (normal and scheduled), get a paginated list of sending push notifications, get information of registered devices, remove registered devices by token, ...

Go to Download


sudiptochoudhury/php-zoho-subscriptions

6 Favers
11476 Downloads

PHP Client Library to Consume Zoho Subscriptions REST API

Go to Download


konfig/snaptrade-php-sdk

1 Favers
23932 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


michtio/craftcms-claude-skills

86 Favers
253 Downloads

Craft CMS 5 expertise as Claude Code skills + a thin PHP API. Consumed by Claude Code (skills plugin) and craftpulse/craft-cortex (MCP prompts/resources).

Go to Download


tfs/sendy

1 Favers
643 Downloads

Consumes Sendy's API and provides a usable class with method processRequest() allowing easy requesting quote as well as completing request.

Go to Download


mijnkantoor/nmbrs

2 Favers
12211 Downloads

SDK to consume NMBRS API in PHP

Go to Download


setono/shipmondo-php-sdk

0 Favers
4506 Downloads

Consume the Shipmondo API with this PHP SDK

Go to Download


perfion/perfion-php-sdk

0 Favers
34192 Downloads

PHP SDK to consume the Perfion API

Go to Download


bernskioldmedia/laravel-fortnox

5 Favers
1845 Downloads

A Laravel package to consume the Fortnox API.

Go to Download


clicksign/clicksign-php

7 Favers
74520 Downloads

PHP client to consume Clicksign JSON API

Go to Download


cubesystems/api-client

0 Favers
5248 Downloads

API Client provides a modular way to consume API's for Laravel.

Go to Download


contoweb/laravel-abacus-api

6 Favers
31 Downloads

Laravel wrapper for Abacus REST API to consume it in a Laravel way.

Go to Download


<< Previous Next >>