Libraries tagged by future
flp/flp
7073 Downloads
FutureLink-Protocol implementation in PHP
enko/dokuwikiobjectrepresentation
47 Downloads
DokuWiki data abstraction from the future
craryprimitiveman/php-resque-scheduler
84 Downloads
php-resque-scheduler is a PHP port of resque-scheduler, which adds support for scheduling items in the future to Resque.
codememory/reflection
119 Downloads
The library is similar to the built-in API class Reflection, but the only difference is that this library caches the entire result and does not work with the built-in Reflection in the future, which improves performance
codecomodo/codecomodo
0 Downloads
The PHP Framework for future
christophlehmann/treecleaner
6 Downloads
Hides duplicates in page- and category-tree in the backend; Developed for lighter user management / editors with overlapping mount points; Hopefully core functionality in the future
bmilesp/email_queue
19 Downloads
Queue, Throttle, and Send-In-the-Future emails
blinktag/laravel-lazydev
14 Downloads
Finds TODO and FIXME annotations that past-you left in the code for future-you to deal with
bleeld/think-token
2 Downloads
This is a collection of JWT Token remote file management drivers developed in factory mode. Users can use different JWT extensions according to their business needs. In the future, developers can further improve more token drivers according to their own needs.
bleeld/think-oss
24 Downloads
This is a collection of OSS remote file management drivers developed in factory mode. Users can use different OSS extensions according to their business needs. In the future, developers can further improve more OSS drivers according to their own needs.
bigcrunch/gateio-api
4 Downloads
Welcome to Gate API APIv4 provides spot, margin and futures trading operations. There are public APIs to retrieve the real-time market statistics, and private APIs which needs authentication to trade on user's behalf.
bigcrunch/gateapi-php
239 Downloads
Welcome to Gate.io API APIv4 provides spot, margin and futures trading operations. There are public APIs to retrieve the real-time market statistics, and private APIs which needs authentication to trade on user's behalf.
beapi/missed-schedule
30 Downloads
Publish future post when the publication date has passed and WordPress fails.
andrefigueira/laramailer
66 Downloads
A simple mailing package using Laravel Mail and Blade for sending emails with an expressive syntax, and also the ability to store emails in a database for future viewing
alissonlinneker/statuspage-php-sdk
4 Downloads
# 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