When interacting with MBurger API pass arguments as:

  • GET querystring parameters

  • POST parameters presented as application/x-www-form-urlencoded or a mix of both GET and POST parameters

  • Some write APIs allow arguments application/json attributes.

  • File uploads expects multipart/form-data, which is a fancy way of asking you to send most parameters as application/x-www-form-urlencoded key/value pairs, but send files in their native content type.

Query Builder

Some GET request like for blocks and sections adopts a powerful query builder system.

Using 3 parameters include, filter and sort in the request query string the client can build requests that reflects perfectly their needs.

Check in which APIs this system is available to see all the available parameters.


MBurger uses some HTTP headers to handle requests.

In particular, they are used to authenticate and to know which kind of data one should expect from the client and vice versa.

All used headers are shown in the table below, but they can change based on which API you are calling.

Last updated