Libraries tagged by limiting

Adds a custom health check endpoint with rate limiting to your WordPress site. Supports a customizable endpoint slug through a constant.

Go to Download

Enterprise-grade rate limiting for Laravel APIs with quotas, analytics, and abuse protection.

Go to Download

A WordPress MU plugin that prevents brute force attacks by limiting the number of failed login attempts during a browser session.

Go to Download

Rate Limiting Library With Token Bucket Algorithm

Go to Download

Request limiting for silex

Go to Download

Laravel API Response is a powerful and flexible package that provides a standardized way to structure API responses in Laravel applications. It offers a range of features to enhance your API development experience, including consistent response formatting, conditional responses, pagination support, rate limiting, and more.

Go to Download

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

Go to Download

PSR Middleware for limiting api client requests

Go to Download

Multi-period rate limiting for Laravel applications with minute, hour, and day limits

Go to Download

A package to create a GraphQL API with MySQL, JWT Authentication, and Rate Limiting

Go to Download

Advanced error logger with multiple transport options and rate limiting

Go to Download

A PHP Library that seamlessly integrate limiting into your platform, supports Redis ,FileSystem , Datbases such as SQL Relational Database.

Go to Download

Request rate limiting using Predis.

Go to Download

Advanced, secure OTP (Email/SMS/WhatsApp) package for Laravel with hashed codes, TTL, rate limiting, one-time use, events, and drivers.

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