Libraries tagged by alisms
arthuryinzhen/laravel-ali-sms
5 Downloads
ali sms for laravel5.2
yonghua4413/ali-sms
66 Downloads
阿里大鱼 阿里新版短信
silentlun/yii2-alisms
11 Downloads
Alisms extension for YII2
shangxin/yii2-alisms
10 Downloads
the message service of ali
lanizz/laravel-alisms
80 Downloads
Laravel5阿里云短信服务提供者
fbao/ali-sms
57 Downloads
阿里云官方短信sdk
smater/ali-sms
381 Downloads
阿里云短信发送
vingin007/esign
171 Downloads
dshufeng/dysms
17 Downloads
阿里短信-适用Laravel、Yii、Thinkphp等任何PHP项目...
alissonphp/lumen-api-skeleton
8 Downloads
Lumen API skeleton with JWT to manager tokens, Socialite to OAuth Providers, MongoDB driver and Predis to Redis cache storage.
alissonpelizaro/ssh_powershell
26 Downloads
Remote Powershell SSH access
alissn/laravel-dumper
143 Downloads
brianalzatedeveloper/apismsrest
7 Downloads
This Package contains methods to connet to api sms correctly, send and receive information securetly
alisson-nascimento/json2class
36 Downloads
JSON parse to Classes
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