HTTP API
B.1 REST Core Interface
Keenetic Extra HTTP API lets you develop a custom application, that will access Keenetic
Extra settings using simple HTTP methods, such as GET and POST.
The base URL for all operations is
/rci
, that simply stands for REST Core Interface. It
replaces the
, which is now deprecated but continues to be functional.
B.1.1 Resource Location
RCI is based on the Keenetic Extra command tree. Device settings are mapped to RCI
resources in such a way that every “
a b c
” command corresponds to the
/rci/a/b/c
URL.
As a result, hereby
gives you a complete picture of all RCI resources
and their parameters. The words “command” and “resource” are used interchangeably in
this manual.
Parameters are listed in the Arguments table of each command. They can be passed as
part of the request using HTTP query:
/rci/a/b/c?parameter=value
. Unless otherwise
specified for a certain command, query parameters are optional. Multiple parameters
should be separated by ampersand (&) characters.
Parameters can also be passed in the POST request body, as described in
.
B.1.2 Methods
Method semantics depend on the type of resource. There are three types of resources in
RCI:
• Settings
• Actions
• Background processes
B.1.2.1 Settings
Settings are device configuration elements. You can view, modify, or delete settings using
standard HTTP methods.
GET
Retrieve settings.
B
Keenetic Extra (KN-1710) — Command Reference Guide
335
Summary of Contents for EXTRA KN-1710
Page 2: ......
Page 6: ...Command Reference Guide Keenetic Extra KN 1710 6 Contents Overview...
Page 20: ...Command Reference Guide Keenetic Extra KN 1710 20 Chapter 1 Product Overview...
Page 26: ...Command Reference Guide Keenetic Extra KN 1710 26 Chapter 2 Introduction to the CLI...
Page 322: ...Command Reference Guide Keenetic Extra KN 1710 322 Chapter 3 Command Reference...
Page 332: ...Command Reference Guide Keenetic Extra KN 1710 332 Glossary...
Page 348: ...Command Reference Guide Keenetic Extra KN 1710 348 Appendix C SNMP MIB...
