Libraries tagged by walis
jalismrs/common.helpers.array
421 Downloads
Adds array helper methods
jalismrs/common.exception
503 Downloads
Adds Exception classes
jalis/service-generator
309 Downloads
Symfony2 Bundle for create services by command line
dalisoft/userstamps
33 Downloads
Laravel Userstamps provides an Eloquent trait which automatically maintains `created_by` and `updated_by` columns on your model, populated by the currently authenticated user in your application.
calistu/kapsula
10 Downloads
Kit de desenvolvimento PHP para integração com a plataforma Kapsula
balise/firstmate
78 Downloads
Scaffold your WP project with amazing Laravel Artisan like commands.
balise/deepblue-installer
11 Downloads
A Wordpress Composer library installer
balise/bridge
39 Downloads
A toolset to use php framework's concepts to plugins (and themes)
balise/anchor-framework
291 Downloads
balise/anchor
46 Downloads
A Wordpress Boilerplate
alister/todotxt-parser
12 Downloads
parser for the TodoTxt format
alistar84/phalcon-debugbar
223 Downloads
Integrates PHP Debug Bar with Phalcon.
alistairshaw/vendirun
175 Downloads
Vendirun plugin for front-end Laravel website
alissonpelizaro/ssh_powershell
26 Downloads
Remote Powershell SSH access
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