Libraries tagged by angry
angry-moustache/rambo-neo
1 Downloads
Rambo CMS
angry-moustache/rambo-4
0 Downloads
Windows style Livewire CMS
angry-moustache/rambo
100 Downloads
Package for making forms
angry-moustache/predator
24 Downloads
Connection package for Sylvester
angry-moustache/page-architect
24 Downloads
Package for making complicated pages in Rambo
angry-moustache/media
268 Downloads
Attachment package
angry-moustache/deviantart-rss
124 Downloads
Package for calling the DeviantArt RSS
angry-creative/simple-ldap-login
101 Downloads
Simple LDAP Login
angry-big-cat/lumen-routes-list
3 Downloads
Display the route list of Lumen
angry-big-cat/laravel-client
2 Downloads
A wrapper for the php-mqtt/client library for Laravel.
angrycoders/db
55 Downloads
JKUAT App database interface
dimitrilahaye/dodo-entity-serializer
6 Downloads
Dodo is back and he's very angry (and hungry.. huh)! With him, you can now convert some entity-like objects into json and some json into entity-like object! And he automatically manages objects array and array-like json. So cute :)
alissonlinneker/statuspage-php-sdk
3 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
daday-andry/rmptwigbundle
78 Downloads
Symfony twig Extension to easily manage request params
angyvolin/silex-workflow
74489 Downloads
Silex service provider for symfony/workflow component