access_via_api
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
access_via_api [2018/12/11 12:04] – [List of dashboard's blocks] emozolyak | access_via_api [2019/03/12 14:45] – akuzmuk | ||
---|---|---|---|
Line 910: | Line 910: | ||
Example of the response: | Example of the response: | ||
- | < | + | < |
{ | { | ||
" | " | ||
Line 2107: | Line 2107: | ||
|**regid**| int |ID of the source register for value | | |**regid**| int |ID of the source register for value | | ||
+ | |||
+ | |||
+ | ===== Managing recipes list ===== | ||
+ | |||
+ | |||
+ | To get a list of all recipes, you must perform a GET request on the URL like this: http:// | ||
+ | |||
+ | To obtain information about a particular recipe, you must perform a following GET request on a URL ' | ||
+ | |||
+ | In the headers, it is necessary to pass API key. For example: | ||
+ | |||
+ | X-WH-APIKEY: | ||
+ | |||
+ | Also, in the headers, you must specify the desired data exchange format. Currently, only the JSON format is supported. | ||
+ | |||
+ | Accept: application/ | ||
+ | Content-Type: | ||
+ | |||
+ | Example of a query for all recipes data: | ||
+ | |||
+ | ***URL:** http:// | ||
+ | ***Method: | ||
+ | *Headers: | ||
+ | |||
+ | Accept: application/ | ||
+ | Content-Type: | ||
+ | Accept-Encoding: | ||
+ | X-WH-APIKEY: | ||
+ | |||
+ | Response example: | ||
+ | < | ||
+ | [ | ||
+ | { | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | }, | ||
+ | { | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | } | ||
+ | ] | ||
+ | </ | ||
+ | |||
+ | ^Block attributes: | ||
+ | |**id**| int |Unique recipe identifier | | ||
+ | |**title**| string |Title of recipe | | ||
+ | |**category**| string |Category of recipe | | ||
+ | |**description**| string |Description of recipe | | ||
+ | |**regs_values**| string |List of register values in following format: reg_id1%%^%%new_value%%|%%reg_id2%%^%%new_value%%|%%reg_id3%%^%%new_value | | ||
+ | |**allowed_for_roles**| string |Comma-separated role IDs who can access this recipe | | ||
+ | |**disabled**| int |Flag that shows if recipe is disabled | | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | To update a register values in particular recipe it's necessary to execute PUT-request on URL http:// | ||
+ | |||
+ | In the headers, it is necessary to pass API key. For example: | ||
+ | |||
+ | X-WH-APIKEY: | ||
+ | |||
+ | Also, in the headers, you must specify the desired data exchange format. Currently, only the [[https:// | ||
+ | |||
+ | |||
+ | Accept: application/ | ||
+ | Content-Type: | ||
+ | |||
+ | |||
+ | In the request body, the json-object with at least of property be passed. | ||
+ | < | ||
+ | {" | ||
+ | </ | ||
+ | |||
+ | Example of updating title and register values to the recipe with ID = 5: | ||
+ | |||
+ | ***URL**: http:// | ||
+ | ***Method**: | ||
+ | *Headers: | ||
+ | |||
+ | Accept: application/ | ||
+ | Content-Type: | ||
+ | Accept-Encoding: | ||
+ | X-WH-APIKEY: | ||
+ | |||
+ | Request body: | ||
+ | |||
+ | {" | ||
+ | |||
+ | If the request is valid, API will return HTTP-code 200. | ||
access_via_api.txt · Last modified: 2023/03/02 10:53 by emozolyak