How to read the interface document? Interface documentation has so many benefits, so how do we read it? Here we use the interface document of job function email list WeChat subscription notification as learning material. As shown in job function email list the figure above, the interface is usually divided into four parts: request method, url, request parameters, and return parameters: 1) Request method: The commonly used methods are the following four -
GET , PUT, POST, DELETE. A GET request will send job function email list a request for data to the database to obtain information. This request is just like the select operation of the database, it is only used to query the data, it will not modify or add data, and will not affect the content of the resource, that is, the request will not produce side effects. Unlike GET, PUT requests send data to the server, thereby changing the information. job function email list This request is like the update operation of the database, which is used to modify the content of the data, but does not increase the type of data. The POST request is similar to the
PUT request in that it sends data to the server, but job function email list the request will change the type of data and other resources , just like t he insert operation of the database, it will create new content. Almost all submission operations currently use POST job function email list requests. The DELETE request, as the name suggests, is used to delete a resource, and the request is like the delete operation of the database. This concept product manager can simply understand, generally do not test