Libraries tagged by futures

# 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

Replaces accents from future uploads and has wp-cli command which you can use to sanitize current content.

Go to Download

Message queue utitlity library for applications with queue and topic utilization. This library support Aliyun MNS service and will be support more message queue types in the future.

Go to Download

php-resque-scheduler is a PHP port of resque-scheduler, which adds support for scheduling items in the future to Resque.

Go to Download

Access Traffic Scotland's Current Incidents, Live Traffic Cameras, Unplanned Events, Roadworks, Future Roadworks, Traffic Status, Variable Message Signs and Journey Times.

Go to Download

Access Traffic Scotland's Current Incidents, Live Traffic Cameras, Unplanned Events, Roadworks, Future Roadworks, Traffic Status, Variable Message Signs and Journey Times.

Go to Download

Legacy and future builds of the Ozone framework, originally packaged for wikidot.org.

Go to Download

Do not use - this is just to avoid having to use the git/github repository types, and will be dropped in future

Go to Download

Simple implementation of \Nette\Localization\ITranslator interface. Just print the key as is. Usefull when you have no time for managing gettext translation but want translatable application in the future.

Go to Download

This Package will provide every data a site owner may need in the future :D

Go to Download

Wrapper for OrientTech's PhpOrient driver. (May evolve into a basic ODM in the future).

Go to Download

Transporter is a futuristic way to send API requests in PHP. This is an OOP approach to handle API requests.

Go to Download

Tool for loading or deploying CSS and JS files into web pages

Go to Download

Grido - DataGrid for Nette Framework

Go to Download

Gettext translator for Latte template

Go to Download