HTTP Verbs
This document covers information about HTTP verbs used by the wunderbon API
TL;DR
@TODO HTTP VERBS
The wunderbon API enables you to develop having all possible CRUD (create, retrieve, update, delete) operations. API guidelines suggest using a specific HTTP Verb on a specific type of call made to the server. wunderbon follows the common standards (this is very subjective) so get an overview here:
Supported HTTP Verbs
Where possible, the wunderbon API strives to use appropriate HTTP verbs for each action.
REST API
The wunderbon API supports all recommended standard
HTTP Verbs. But this does not apply on all resources. See details of the resources (entities) for supportedHTTP Verbson resource level.
GET | Used for retrieving resources. |
POST | Used for creating resources. |
DELETE | Used for deleting resources. |
HEAD | Can be issued against any resource to get just the HTTP header info. |
OPTIONS | Used to describe the communication options for the target resource. |
PATCH | Used for partial modifications to a resource. |
TRACE | Used for message loop-back test along the path to the target resource, providing a useful debugging mechanism. |
Updated almost 3 years ago
Continue with our guided tour. Now, we would like to tell you more about which HTTP Status Codes you should expect to retrieve from the wunderbon API ...