Skip to main content
Version: 2.10

Control API

The control API can be used to

  • expose APISIX internal state
  • control the behavior of a single isolate APISIX data panel

By default, the control API server is enabled and listens to 127.0.0.1:9090. You can change it via the control section under apisix in conf/config.yaml:

apisix:  ...  enable_control: true  control:    ip: "127.0.0.1"    port: 9090

Note that the control API server should not be configured to listen to the public traffic!

Control API Added via plugin#

Plugin can add its control API when it is enabled. Some plugins in APISIX have added their own control APIs. If you are interested in these APIs, please refer to their documentation.

Plugin independent Control API#

Here is the supported API:

GET /v1/schema#

Introduced since v2.2.

Return the jsonschema used by this APISIX instance in the format below:

{    "main": {        "route": {            "properties": {...}        },        "upstream": {            "properties": {...}        },        ...    },    "plugins": {        "example-plugin": {            "consumer_schema": {...},            "metadata_schema": {...},            "schema": {...},            "type": ...,            "priority": 0,            "version": 0.1        },        ...    },    "stream-plugins": {        "mqtt-proxy": {            ...        },        ...    }}

For plugins part, only enabled plugins will be returned. Some plugins may lack of fields like consumer_schema or type, it is depended on by the plugin's definition.

GET /v1/healthcheck#

Introduced since v2.3.

Return current health check status in the format below:

[    {        "healthy_nodes": [            {                "host": "127.0.0.1",                "port": 1980,                "priority": 0,                "weight": 1            }        ],        "name": "upstream#/upstreams/1",        "nodes": [            {                "host": "127.0.0.1",                "port": 1980,                "priority": 0,                "weight": 1            },            {                "host": "127.0.0.2",                "port": 1988,                "priority": 0,                "weight": 1            }        ],        "src_id": "1",        "src_type": "upstreams"    },    {        "healthy_nodes": [            {                "host": "127.0.0.1",                "port": 1980,                "priority": 0,                "weight": 1            }        ],        "name": "upstream#/routes/1",        "nodes": [            {                "host": "127.0.0.1",                "port": 1980,                "priority": 0,                "weight": 1            },            {                "host": "127.0.0.1",                "port": 1988,                "priority": 0,                "weight": 1            }        ],        "src_id": "1",        "src_type": "routes"    }]

Each entry contains fields below:

  • src_type: where the health checker comes from. The value is one of ["routes", "services", "upstreams"].
  • src_id: the id of object which creates the health checker. For example, if Upstream object with id 1 creates a health checker, the src_type is upstreams and the src_id is 1.
  • name: the name of the health checker.
  • nodes: the target nodes of the health checker.
  • healthy_nodes: the healthy node known by the health checker.

User can also use /v1/healthcheck/$src_type/$src_id can get the status of a health checker.

For example, GET /v1/healthcheck/upstreams/1 returns:

{    "healthy_nodes": [        {            "host": "127.0.0.1",            "port": 1980,            "priority": 0,            "weight": 1        }    ],    "name": "upstream#/upstreams/1",    "nodes": [        {            "host": "127.0.0.1",            "port": 1980,            "priority": 0,            "weight": 1        },        {            "host": "127.0.0.2",            "port": 1988,            "priority": 0,            "weight": 1        }    ],    "src_id": "1",    "src_type": "upstreams"}

POST /v1/gc#

Introduced since v2.8.

Trigger a full GC in the http subsystem. Note that when you enable stream proxy, APISIX will run another Lua VM for the stream subsystem. It won't trigger a full GC in this Lua VM .

Get /v1/routes#

Introduced since v3.0.

Return all routes info in the format below:

[  {    "update_count": 0,    "value": {      "priority": 0,      "uris": [        "/hello"      ],      "id": "1",      "upstream": {        "scheme": "http",        "pass_host": "pass",        "nodes": [          {            "port": 1980,            "host": "127.0.0.1",            "weight": 1          }        ],        "type": "roundrobin",        "hash_on": "vars"      },      "status": 1    },    "clean_handlers": {},    "has_domain": false,    "orig_modifiedIndex": 1631193445,    "modifiedIndex": 1631193445,    "key": "/routes/1"  }]

Get /v1/route/{route_id}#

Introduced since v3.0.

Return specific route info with route_id in the format below:

{  "update_count": 0,  "value": {    "priority": 0,    "uris": [      "/hello"    ],    "id": "1",    "upstream": {      "scheme": "http",      "pass_host": "pass",      "nodes": [        {          "port": 1980,          "host": "127.0.0.1",          "weight": 1        }      ],      "type": "roundrobin",      "hash_on": "vars"    },    "status": 1  },  "clean_handlers": {},  "has_domain": false,  "orig_modifiedIndex": 1631193445,  "modifiedIndex": 1631193445,  "key": "/routes/1"}