Libraries tagged by alisms

arthuryinzhen/laravel-ali-sms

0 Favers
5 Downloads

ali sms for laravel5.2

Go to Download


yonghua4413/ali-sms

0 Favers
66 Downloads

阿里大鱼 阿里新版短信

Go to Download


silentlun/yii2-alisms

0 Favers
11 Downloads

Alisms extension for YII2

Go to Download


shangxin/yii2-alisms

1 Favers
10 Downloads

the message service of ali

Go to Download


lanizz/laravel-alisms

0 Favers
80 Downloads

Laravel5阿里云短信服务提供者

Go to Download


fbao/ali-sms

0 Favers
57 Downloads

阿里云官方短信sdk

Go to Download


smater/ali-sms

0 Favers
381 Downloads

阿里云短信发送

Go to Download


vingin007/esign

0 Favers
171 Downloads

Go to Download


dshufeng/dysms

0 Favers
17 Downloads

阿里短信-适用Laravel、Yii、Thinkphp等任何PHP项目...

Go to Download


alissonphp/lumen-api-skeleton

21 Favers
8 Downloads

Lumen API skeleton with JWT to manager tokens, Socialite to OAuth Providers, MongoDB driver and Predis to Redis cache storage.

Go to Download


alissonpelizaro/ssh_powershell

2 Favers
26 Downloads

Remote Powershell SSH access

Go to Download


alissn/laravel-dumper

2 Favers
143 Downloads

Go to Download


brianalzatedeveloper/apismsrest

0 Favers
7 Downloads

This Package contains methods to connet to api sms correctly, send and receive information securetly

Go to Download


alisson-nascimento/json2class

1 Favers
36 Downloads

JSON parse to Classes

Go to Download


alissonlinneker/statuspage-php-sdk

0 Favers
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

Go to Download


<< Previous Next >>