When interacting with MBurger API pass arguments as:
POSTparameters presented as
application/x-www-form-urlencodedor a mix of both
- Some write APIs allow arguments
- File uploads expects
multipart/form-data, which is a fancy way of asking you to send most parameters as
application/x-www-form-urlencodedkey/value pairs, but send files in their native content type.
GETrequest like for blocks and sections adopts a powerful query builder system.
Using 3 parameters
sortin 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.
Define the data type that client is expecting in response. For API, it should always be
Contains the token to authenticate every API call.
Define the API version you want to use. The minimum and actual is 3.
Allows MBurger to authenticate mobile users. Required only for APIs regarding mobile users.
Define the data type that MBurger is expecting in request data. Required when data in POSTed to MBurger, normally it is