Libraries tagged by curl delete

Provides REST request methods. Mapper bundle for php internal curl library

Go to Download

Rest client to make GET, POST, PUT, DELETE, PATCH, etc calls.

Go to Download

CurlHelper is a streamlined PHP utility for easy cURL usage, supporting GET, POST, PUT, and DELETE methods. It simplifies HTTP requests by offering straightforward options and header settings, making web API interactions more accessible and efficient.

Go to Download

Curl Wrapper for PHP

Go to Download

一个轻量级的PHP网络操作类，实现GET、POST、PUT、DELETE常用操作，出错自动重试，支持链式写法

Go to Download

Create Rest Request (POST,GET,PUT,DELETE,...)

Go to Download

Provides REST request methods. Mapper bundle for php internal curl library

Go to Download

A small, lightweight utility to perform curl calls using GET, POST, PUT, PACTH, DELETE, HEAD, TRACE, OPTIONS methods...

Go to Download

This is a simple cURL library to dispatch HTTP GET, POST, PUT and DELETE request, easily.

Go to Download

Send your self-defined HTTP request to somewhere,and you do not care anything else

Go to Download

Provides REST request methods. Mapper bundle for php internal curl library

Go to Download

Make request http cross site

Go to Download

easy http url in PHP. (get, post, put, delete for both 'curl' and 'file_get_content')

Go to Download

The HttpClient PHP package is a package designed for making HTTP requests using cURL. This package simplifies the process of sending GET, POST, PUT, PATCH, and DELETE requests, along with the ability to set custom headers, to external APIs or web services.

Go to Download

# 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