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:

6464

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 supported HTTP Verbs on resource level.

GETUsed for retrieving resources.
POSTUsed for creating resources.
DELETEUsed for deleting resources.
HEADCan be issued against any resource to get just the HTTP header info.
OPTIONSUsed to describe the communication options for the target resource.
PATCHUsed for partial modifications to a resource.
TRACEUsed for message loop-back test along the path to the target resource, providing a useful debugging mechanism.

What’s Next

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 ...