HTTP API Testing Tool
https://post.jsonin.com
Supports all HTTP methods including GET, POST, PUT, DELETE, HEAD, TRACE, PATCH, OPTIONS

Supports quick addition and batch import of request headers (Headers) 

Quick addition: Cookies
Authorization
Accept
Accept-Language
Accept-Encoding
Connection
Cache-Control
X-Forwarded-For (Proxy)
X-Real-IP (Proxy)
X-Requested-With
Content-Type: Form
Content-Type: Multipart
Content-Type: XML

Bulk Import: Paste the original request headers copied from the browser F12 (one key: value per line): Hint: In the browser, press F12 to open the developer tools → Network tab → Click the request → Headers tab → Right-click the request header area and select "Copy all" to copy.  

The standard HTTP protocol supports six request methods:
    GET: GET is arguably the most common method. It essentially involves sending a request to retrieve a resource from the server. The resource is returned to the client along with a set of HTTP headers and presentation data (such as HTML text, or images or videos, etc.). In GET requests, presentation data is never included;
    HEAD: HEAD is essentially the same as GET, with the main difference being that HEAD does not contain presentation data—it only includes HTTP header information. Some might think this method is not very useful, but that's not the case. Imagine a business scenario: if you want to determine whether a resource exists, you might typically use GET, but using HEAD in this case makes the intention clearer.
    PUT: This method is relatively uncommon. HTML forms also do not support this. Essentially, PUT and POST are very similar, both sending data to the server, but there is a significant difference between them. PUT typically specifies the location of the resource, while POST does not; the location of the data submitted via POST is determined by the server. For example: consider a URL for submitting a blog post, /addBlog. If using PUT, the submitted URL would be something like /addBlog/abc123, where abc123 is the address of that blog post. If using POST, the server would inform the client of the address after submission. Most blogs work this way. Clearly, PUT and POST have different purposes. Which one to use depends on the specific business scenario;
    DELETE: Delete a resource. This is also relatively uncommon, but it is used in some places, such as Amazon's S3 cloud service, to delete resources;
    POST: Submit data to the server. This method is widely used and almost all submission operations rely on it.
   OPTIONS: It is used to get the methods supported by the current URL. If the request is successful, it will include a header named "Allow" in the HTTP header, with the value being the supported methods, such as "GET, POST".
Usually, we use GET, PUT, POST, DELETE requests to simulate server operations for adding, deleting, updating, and querying databases.
POST: create (add)
     DELETE: delete (delete)
     Put : update(更新)
     GET: select (query)

Online POST, Online GET, Online API Testing Tool:https://post.jsonin.com