Libraries tagged by rate-limiting

Guardian is a PHP package that provides a way to wrap HTTP requests so they don't exceed Rate Limiting rules and controls Error Handling

Go to Download

Rate limiting abstraction which, in conjunction with your application's cache, provides an easy way to limit requests during a specified window of time.

Go to Download

A sweet, simple PHP class for rate limiting API requests.

Go to Download

This is the behavior for Yii2 Http Client, which provides rate limiting for requests per second or per minute. It is useful for connecting web services with rate limiting.

Go to Download

PHP rate limiting library with Leaky Bucket Algorithm

Go to Download

A simple PHP library for rate limiting API requests.

Go to Download

Laravel queue rate limiting.

Go to Download

A package for OTP authentication with Redis rate limiting.

Go to Download

(API) Rate limiting requests in CakePHP

Go to Download

Standalone component that facilitates rate-limiting functionality. Also provides a middleware designed for API and/or other application endpoints.

Go to Download

Standalone component that facilitates rate-limiting functionality. Also provides a middleware designed for API and/or other application endpoints.

Go to Download

PHP rate limiting library with Token Bucket and Leaky Bucket Algorithms, based on palepurple/rate-limit, grandson to touhonoob/rate-limit, and jeroenvisser101/LeakyBucket

Go to Download

Rate Limiting Library With Token Bucket Algorithm

Go to Download

A simple but fully featured Echonest API wrapper, with auto rate limiting and Guzzle 6 support

Go to Download

# Code of Conduct Please don't abuse the API, and please report all feature requests and issues to https://support.atlassian.com/contact # Rate Limiting Each API token is limited to 1 request / second as measured on a 60 second rolling window. To get this limit increased, please contact us at https://support.atlassian.com/contact Error codes 420 or 429 indicate that you have exceeded the rate limit and the request has been rejected. # Basics ## HTTPS It's required ## URL Prefix In order to maintain version integrity into the future, the API is versioned. All calls currently begin with the following prefix: https://api.statuspage.io/v1/ ## RESTful Interface Wherever possible, the API seeks to implement repeatable patterns with logical, representative URLs and descriptive HTTP verbs. Below are some examples and conventions you will see throughout the documentation. * Collections are buckets: https://api.statuspage.io/v1/pages/asdf123/incidents.json * Elements have unique IDs: https://api.statuspage.io/v1/pages/asdf123/incidents/jklm456.json * GET will retrieve information about a collection/element * POST will create an element in a collection * PATCH will update a single element * PUT will replace a single element in a collection (rarely used) * DELETE will destroy a single element ## Sending Data Information can be sent in the body as form urlencoded or JSON, but make sure the Content-Type header matches the body structure or the server gremlins will be angry. All examples are provided in JSON format, however they can easily be converted to form encoding if required. Some examples of how to convert things are below: // JSON { "incident": { "name": "test incident", "components": ["8kbf7d35c070", "vtnh60py4yd7"] } } // Form Encoded (using curl as an example): curl -X POST https://api.statuspage.io/v1/example \ -d "incident[name]=test incident" \ -d "incident[components][]=8kbf7d35c070" \ -d "incident[components][]=vtnh60py4yd7" # Authentication

Go to Download