Table of Contents

Route

API:/apisix/admin/routes/{id}?ttl=0

Description:Route matches requests based on preset rules, and loads the appropriate plugin according to the matching result, then forwarding requests to target Upstream.

Request Methods:

MethodRequest URIRequest BodyDescription
GET/apisix/admin/routes/{id}NULLFetch resource
PUT/apisix/admin/routes/{id}{...}Create resource by ID
POST/apisix/admin/routes{...}Create resource, and ID is generated by server
DELETE/apisix/admin/routes/{id}NULLRemove resource
PATCH/apisix/admin/routes/{id}{...}Standard PATCH. Update some attributes of the existing Route, and other attributes not involved will remain as they are; if you want to delete an attribute, set the value of the attribute Set to null to delete; especially, when the value of the attribute is an array, the attribute will be updated in full
PATCH/apisix/admin/routes/{id}/{path}{...}SubPath PATCH, specify the attribute of Route to be updated through {path}, update the value of this attribute in full, and other attributes that are not involved will remain as they are. The difference between the two PATCH can refer to the following examples

URI Request Parameters:

parameterRequiredTypeDescriptionExample
ttlFalseAuxiliaryExpires after target secondsttl=1

Request Body Parameters:

ParameterRequiredTypeDescriptionExample
nameFalseAuxiliaryIdentifies route names.customer-xxxx
descFalseAuxiliaryroute description, usage scenarios, and more.customer xxxx
uriTrueMatch RulesIn addition to full matching such as /foo/bar/foo/gloo, using different Router allows more advanced matching, see Router for more.“/hello”
hostFalseMatch RulesCurrently requesting a domain name, such as foo.com; pan-domain names such as *.foo.com are also supported.“foo.com”
hostsFalseMatch RulesThe host in the form of a list means that multiple different hosts are allowed, and match any one of them.{“foo.com”, “*.bar.com”}
remote_addrFalseMatch RulesThe client requests an IP address: 192.168.1.101, 192.168.1.102, and CIDR format support 192.168.1.0/24. In particular, APISIX also fully supports IPv6 address matching: ::1, fe80::1, fe80::1/64, etc.“192.168.1.0/24”
remote_addrsFalseMatch RulesThe remote_addr in the form of a list indicates that multiple different IP addresses are allowed, and match any one of them.{“127.0.0.1”, “192.0.0.0/8”, “::1”}
methodsFalseMatch RulesIf empty or without this option, there are no method restrictions, and it can be a combination of one or more: GET,POST,PUT,DELETE,PATCH, HEAD,OPTIONS,CONNECT,TRACE.{“GET”, “POST”}
priorityFalseMatch RulesIf different routes contain the same uri, determine which route is matched first based on the attribute priority. Larger value means higher priority. The default value is 0.priority = 10
varsFalseMatch RulesA list of one or more {var, operator, val} elements, like this: {{var, operator, val}, {var, operator, val}, ...}}. For example: {"arg_name", "==", "json"} means that the current request parameter name is json. The var here is consistent with the internal variable name of Nginx, so you can also use request_uri, host, etc. For the operator part, the currently supported operators are ==, ~=,>, <, and ~~. For the > and < operators, the result is first converted to number and then compared. See a list of supported operators{{“arg_name”, “==”, “json”}, {“arg_age”, “>”, 18}}
filter_funcFalseMatch RulesUser-defined filtering function. You can use it to achieve matching requirements for special scenarios. This function accepts an input parameter named vars by default, which you can use to get Nginx variables.function(vars) return vars[“arg_name”] == “json” end
pluginsFalsePluginSee Plugin for more
scriptFalseScriptSee Script for more
upstreamFalseUpstreamEnabled Upstream configuration, see Upstream for more
upstream_idFalseUpstreamEnabled upstream id, see Upstream for more
service_idFalseServiceBinded Service configuration, see Service for more
service_protocolFalseUpstream protocol typeonly grpc and http are supportedhttp is the default value; Must set grpc if using gRPC proxy or gRPC transcode
labelsFalseMatch RulesKey/value pairs to specify attributes{“version”:“v2”,“build”:“16”,“env”:“production”}
enable_websocketFalseAuxiliaryenable websocket(boolean), default false.
create_timeFalseAuxiliaryepoch timestamp in second, will be created automatically if missing1602883670
update_timeFalseAuxiliaryepoch timestamp in second, will be created automatically if missing1602883670

For the same type of parameters, such as host and hosts, remote_addr and remote_addrs cannot exist at the same time, only one of them can be selected. If enabled at the same time, the API will response an error.

Config Example:

{
    "id": "1",                  # id, unnecessary.
    "uri": "/release/a",        # uri
    "uris": ["/a","/b"],        # A set of uri, URL and uris need only have a non-empty one.
    "methods": ["GET","POST"],  # Can fill multiple methods
    "host": "aa.com",           # host
    "hosts": ["a.com","b.com"], # A set of host. Host and hosts only need to be non-empty one.
    "plugins": {},              # Bound plugin
    "priority": 0,              # If different routes contain the same `uri`, determine which route is matched first based on the attribute` priority`, the default value is 0.
    "name": "route-xxx",
    "desc": "hello world",
    "remote_addr": "127.0.0.1", # Client IP
    "remote_addrs": ["127.0.0.1"], # A set of Client IP. Remote_addr and remo-te_addrs only need to be non-empty one.
    "vars": [],                 # A list of one or more `{var, operator, val}` elements
    "upstream_id": "1",         # upstream id, recommended
    "upstream": {},             # upstream, not recommended
    "filter_func": "",          # User-defined filtering function
}

Example:

# Create a route
$ curl http://127.0.0.1:9180/apisix/admin/routes/1 -H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PUT -i -d '
{
    "uri": "/index.html",
    "hosts": ["foo.com", "*.bar.com"],
    "remote_addrs": ["127.0.0.0/8"],
    "methods": ["PUT", "GET"],
    "enable_websocket": true,
    "upstream": {
        "type": "roundrobin",
        "nodes": {
            "39.97.63.215:80": 1
        }
    }
}'

HTTP/1.1 201 Created
Date: Sat, 31 Aug 2019 01:17:15 GMT
...

# Create a route expires after 60 seconds, then it's deleted automatically
$ curl http://127.0.0.1:9180/apisix/admin/routes/2?ttl=60 -H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PUT -i -d '
{
    "uri": "/aa/index.html",
    "upstream": {
        "type": "roundrobin",
        "nodes": {
            "39.97.63.215:80": 1
        }
    }
}'

HTTP/1.1 201 Created
Date: Sat, 31 Aug 2019 01:17:15 GMT
...


# Add an upstream node to the Route
$ curl http://127.0.0.1:9180/apisix/admin/routes/1 -H'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PATCH -i -d '
{
    "upstream": {
        "nodes": {
            "39.97.63.216:80": 1
        }
    }
}'
HTTP/1.1 200 OK
...

After successful execution, upstream nodes will be updated to:
{
    "39.97.63.215:80": 1,
    "39.97.63.216:80": 1
}


# Update the weight of an upstream node to the Route
$ curl http://127.0.0.1:9180/apisix/admin/routes/1 -H'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PATCH -i -d '
{
    "upstream": {
        "nodes": {
            "39.97.63.216:80": 10
        }
    }
}'
HTTP/1.1 200 OK
...

After successful execution, upstream nodes will be updated to:
{
    "39.97.63.215:80": 1,
    "39.97.63.216:80": 10
}


# Delete an upstream node for the Route
$ curl http://127.0.0.1:9180/apisix/admin/routes/1 -H'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PATCH -i -d '
{
    "upstream": {
        "nodes": {
            "39.97.63.215:80": null
        }
    }
}'
HTTP/1.1 200 OK
...

After successful execution, upstream nodes will be updated to:
{
    "39.97.63.216:80": 10
}


# Replace methods of the Route  --  array
$ curl http://127.0.0.1:9180/apisix/admin/routes/1 -H'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PATCH -i -d '{
    "methods": ["GET", "POST"]
}'
HTTP/1.1 200 OK
...

After successful execution, methods will not retain the original data, and the entire update is:
["GET", "POST"]


# Replace upstream nodes of the Route -- sub path
$ curl http://127.0.0.1:9180/apisix/admin/routes/1/upstream/nodes -H'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PATCH -i -d '
{
    "39.97.63.200:80": 1
}'
HTTP/1.1 200 OK
...

After successful execution, nodes will not retain the original data, and the entire update is:
{
    "39.97.63.200:80": 1
}


# Replace methods of the Route -- sub path
$ curl http://127.0.0.1:9180/apisix/admin/routes/1/methods -H'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PATCH -i -d'["POST", "DELETE", " PATCH"]'
HTTP/1.1 200 OK
...

After successful execution, methods will not retain the original data, and the entire update is:
["POST", "DELETE", "PATCH"]

Response Parameters

Return response from etcd currently.

Available Operators

OperatorDescriptionExample
==Equal{“arg_name”, “==”, “json”}
~=Not Equal{“arg_name”, “~=”, “json”}
>Greater Than{“arg_age”, “>”, 24}
<Less Than{“arg_age”, “<”, 24}
~~Regex{“arg_name”, “~~”, “[a-z]+”}

Consider the following example: matching requests whose request name is equal to json, age is greater than 18, and address begins with China:

curl http://127.0.0.1:9180/apisix/admin/routes/1 -H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PUT -i -d '
{
    "uri": "/index.html",
    "vars": [
        ["arg_name", "==", "json"],
        ["arg_age", ">", "18"],
        ["arg_address", "~~", "China.*"]
    ],
    "upstream": {
        "type": "roundrobin",
        "nodes": {
            "39.97.63.215:80": 1
        }
    }
}'

Back to TOC

Service

API:/apisix/admin/services/{id}

Description:A Service is an abstraction of an API (which can also be understood as a set of Route abstractions). It usually corresponds to the upstream service abstraction. Between Route and Service, usually the relationship of N:1.

Request Methods:

MethodRequest URIRequest BodyDescription
GET/apisix/admin/services/{id}NULLFetch resource
PUT/apisix/admin/services/{id}{...}Create resource by ID
POST/apisix/admin/services{...}Create resource, and ID is generated by server
DELETE/apisix/admin/services/{id}NULLRemove resource
PATCH/apisix/admin/services/{id}{...}Standard PATCH. Update some attributes of the existing Service, and other attributes not involved will remain as they are; if you want to delete an attribute, set the value of the attribute Set to null to delete; especially, when the value of the attribute is an array, the attribute will be updated in full
PATCH/apisix/admin/services/{id}/{path}{...}SubPath PATCH, specify the attribute of Service to be updated through {path}, update the value of this attribute in full, and other attributes that are not involved will remain as they are. The difference between the two PATCH can refer to the following examples

Request Body Parameters:

ParameterRequiredTypeDescriptionExample
pluginsFalsePluginSee Plugin for more
upstreamFalseUpstreamEnabled Upstream configuration, see Upstream for more
upstream_idFalseUpstreamEnabled upstream id, see Upstream for more
nameFalseAuxiliaryIdentifies service names.customer-xxxx
descFalseAuxiliaryservice usage scenarios, and more.customer xxxx
labelsFalseMatch RulesKey/value pairs to specify attributes{“version”:“v2”,“build”:“16”,“env”:“production”}
enable_websocketFalseAuxiliaryenable websocket(boolean), default false.
create_timeFalseAuxiliaryepoch timestamp in second, will be created automatically if missing1602883670
update_timeFalseAuxiliaryepoch timestamp in second, will be created automatically if missing1602883670

Config Example:

{
    "id": "1",          # id
    "plugins": {},      # Bound plugin
    "upstream_id": "1", # upstream id, recommended
    "upstream": {},     # upstream, not recommended
    "name": "service-test",
    "desc": "hello world",
    "enable_websocket": true,
}

Example:

$ curl http://127.0.0.1:9180/apisix/admin/services/201  -H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PUT -i -d '
{
    "plugins": {
        "limit-count": {
            "count": 2,
            "time_window": 60,
            "rejected_code": 503,
            "key": "remote_addr"
        }
    },
    "enable_websocket": true,
    "upstream": {
        "type": "roundrobin",
        "nodes": {
            "39.97.63.215:80": 1
        }
    }
}'

HTTP/1.1 201 Created
...


# Add an upstream node to the Service
$ curl http://127.0.0.1:9180/apisix/admin/services/201 -H'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PATCH -i -d '
{
    "upstream": {
        "nodes": {
            "39.97.63.216:80": 1
        }
    }
}'
HTTP/1.1 200 OK
...

After successful execution, upstream nodes will be updated to:
{
    "39.97.63.215:80": 1,
    "39.97.63.216:80": 1
}


# Update the weight of an upstream node to the Service
$ curl http://127.0.0.1:9180/apisix/admin/services/201 -H'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PATCH -i -d '
{
    "upstream": {
        "nodes": {
            "39.97.63.216:80": 10
        }
    }
}'
HTTP/1.1 200 OK
...

After successful execution, upstream nodes will be updated to:
{
    "39.97.63.215:80": 1,
    "39.97.63.216:80": 10
}


# Delete an upstream node for the Service
$ curl http://127.0.0.1:9180/apisix/admin/services/201 -H'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PATCH -i -d '
{
    "upstream": {
        "nodes": {
            "39.97.63.215:80": null
        }
    }
}'
HTTP/1.1 200 OK
...

After successful execution, upstream nodes will be updated to:
{
    "39.97.63.216:80": 10
}


# Replace upstream nodes of the Service
$ curl http://127.0.0.1:9180/apisix/admin/services/201/upstream/nodes -H'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PATCH -i -d '
{
    "39.97.63.200:80": 1
}'
HTTP/1.1 200 OK
...

After successful execution, upstream nodes will not retain the original data, and the entire update is:
{
    "39.97.63.200:80": 1
}

Response Parameters

Return response from etcd currently.

Back to TOC

Consumer

API:/apisix/admin/consumers/{username}

Description:Consumers are consumers of certain types of services and can only be used in conjunction with a user authentication system. Consumer regards the username property as the identity, so only the HTTP PUT method is supported for creating a new consumer.

Request Methods:

MethodRequest URIRequest BodyDescription
GET/apisix/admin/consumers/{username}NULLFetch resource
PUT/apisix/admin/consumers{...}Create resource by username
DELETE/apisix/admin/consumers/{username}NULLRemove resource

Request Body Parameters:

ParameterRequiredTypeDescriptionExample
usernameTrueNameConsumer name
pluginsFalsePluginSee Plugin for more
descFalseAuxiliaryIdentifies route names, usage scenarios, and more.customer xxxx
labelsFalseMatch RulesKey/value pairs to specify attributes{“version”:“v2”,“build”:“16”,“env”:“production”}
create_timeFalseAuxiliaryepoch timestamp in second, will be created automatically if missing1602883670
update_timeFalseAuxiliaryepoch timestamp in second, will be created automatically if missing1602883670

Config Example:

{
    "plugins": {},          # Bound plugin
    "username": "name",     # Consumer name
    "desc": "hello world",  # Consumer desc
}

The binding authentication and authorization plug-in is a bit special. When it needs to be used in conjunction with the consumer, it needs to provide user name, password and other information; on the other hand, when it is bound with route / service, it does not require any parameters. Because at this time, it is based on the user request data to infer which consumer the user corresponds to.

Example:

$ curl http://127.0.0.1:9180/apisix/admin/consumers  -H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PUT -i -d '
{
    "plugins": {
        "key-auth": {
            "key": "auth-one"
        },
        "limit-count": {
            "count": 2,
            "time_window": 60,
            "rejected_code": 503,
            "key": "remote_addr"
        }
    }
}'
HTTP/1.1 200 OK
Date: Thu, 26 Dec 2019 08:17:49 GMT
...

{"node":{"value":{"username":"jack","plugins":{"key-auth":{"key":"auth-one"},"limit-count":{"time_window":60,"count":2,"rejected_code":503,"key":"remote_addr","policy":"local"}}},"createdIndex":64,"key":"\/apisix\/consumers\/jack","modifiedIndex":64},"prevNode":{"value":"{\"username\":\"jack\",\"plugins\":{\"key-auth\":{\"key\":\"auth-one\"},\"limit-count\":{\"time_window\":60,\"count\":2,\"rejected_code\":503,\"key\":\"remote_addr\",\"policy\":\"local\"}}}","createdIndex":63,"key":"\/apisix\/consumers\/jack","modifiedIndex":63},"action":"set"}

Response Parameters

Return response from etcd currently.

Back to TOC

Upstream

API:/apisix/admin/upstreams/{id}

Description:Upstream configuration can be directly bound to the specified Route or it can be bound to Service, but the configuration in Route has a higher priority. The priority behavior here is very similar to Plugin.

Request Methods:

MethodRequest URIRequest BodyDescription
GET/apisix/admin/upstreams/{id}NULLFetch resource
PUT/apisix/admin/upstreams/{id}{...}Create resource by ID
POST/apisix/admin/upstreams{...}Create resource, and ID is generated by server
DELETE/apisix/admin/upstreams/{id}NULLRemove resource
PATCH/apisix/admin/upstreams/{id}{...}Standard PATCH. Update some attributes of the existing Upstream, and other attributes not involved will remain as they are; if you want to delete an attribute, set the value of the attribute Set to null to delete; especially, when the value of the attribute is an array, the attribute will be updated in full
PATCH/apisix/admin/upstreams/{id}/{path}{...}SubPath PATCH, specify the attribute of Upstream to be updated through {path}, update the value of this attribute in full, and other attributes that are not involved will remain as they are. The difference between the two PATCH can refer to the following example

Request Body Parameters:

In addition to the basic complex equalization algorithm selection, APISIX's Upstream also supports logic for upstream passive health check and retry, see the table below.

NameOptionalDescription
typerequiredroundrobin supports the weight of the load, chash consistency hash,ewma minimum latency ,pick one of them.see https://en.wikipedia.org/wiki/EWMA_chart for details
nodesrequired if k8s_deployment_info not configuredHash table, the key of the internal element is the upstream machine address list, the format is Address + Port, where the address part can be IP or domain name, such as 192.168.1.100:80, foo.com:80, etc. Value is the weight of the node. In particular, when the weight value is 0, it has a special meaning, which usually means that the upstream node is invalid and never wants to be selected.
k8s_deployment_inforequired if nodes not configuredfields: namespacedeploy_nameservice_nameportbackend_type, port is number, backend_type is pod or service, others is string.
hash_onoptionalThis option is only valid if the type is chash. Supported types vars(Nginx variables), header(custom header), cookie, consumer, the default value is vars.
keyoptionalThis option is only valid if the type is chash. Find the corresponding node id according to hash_on and key. When hash_on is set as vars, key is the required parameter, for now, it support nginx built-in variables like uri, server_name, server_addr, request_uri, remote_port, remote_addr, query_string, host, hostname, arg_***, arg_*** is arguments in the request line, Nginx variables list. When hash_on is set as header, key is the required parameter, and header name is customized. When hash_on is set to cookie, key is the required parameter, and cookie name is customized. When hash_on is set to consumer, key does not need to be set. In this case, the key adopted by the hash algorithm is the consumer_name authenticated. If the specified hash_on and key can not fetch values, it will be fetch remote_addr by default.
checksoptionalConfigure the parameters of the health check. For details, refer to health-check.
retriesoptionalPass the request to the next upstream using the underlying Nginx retry mechanism, the retry mechanism is enabled by default and set the number of retries according to the number of backend nodes. If retries option is explicitly set, it will override the default value. 0 means disable retry mechanism.
timeoutoptionalSet the timeout for connection, sending and receiving messages.
nameoptionalIdentifies upstream names
descoptionalupstream usage scenarios, and more.
pass_hostoptionalpass pass the client request host, node not pass the client request host, using the upstream node host, rewrite rewrite host by the configured upstream_host.
upstream_hostoptionalThis option is only valid if the pass_host is rewrite.
labelsoptionalKey/value pairs to specify attributes
create_timeoptionalepoch timestamp in second, like 1602883670, will be created automatically if missing
update_timeoptionalepoch timestamp in second, like 1602883670, will be created automatically if missing

Config Example:

{
    "id": "1",                  # id
    "retries": 1,               # retry times
    "timeout": {                # Set the timeout for connection, sending and receiving messages.
        "connect":15,
        "send":15,
        "read":15,
    },
    "nodes": {"host:80": 100},  # Upstream machine address list, the format is `Address + Port`
    "k8s_deployment_info": {    # kubernetes deployment info
        "namespace": "test-namespace",
        "deploy_name": "test-deploy-name",
        "service_name": "test-service-name",
        "backend_type": "pod",    # pod or service
        "port": 8080
    },
    "type":"roundrobin",        # chash or roundrobin
    "checks": {},               # Health check parameters
    "hash_on": "",
    "key": "",
    "name": "upstream-for-test",
    "desc": "hello world",
}

Example:

$ curl http://127.0.0.1:9180/apisix/admin/upstreams/100  -H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -i -X PUT -d '
{
    "type":"roundrobin",
    "nodes":{
        "127.0.0.1:80":1,
        "127.0.0.2:80":2,
        "foo.com:80":3
    }
}'
HTTP/1.1 201 Created
Date: Thu, 26 Dec 2019 04:19:34 GMT
Content-Type: text/plain
...


# Add a node to the Upstream
$ curl http://127.0.0.1:9180/apisix/admin/upstreams/100 -H'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PATCH -i -d '
{
    "nodes": {
        "39.97.63.216:80": 1
    }
}'
HTTP/1.1 200 OK
...

After successful execution, nodes will be updated to:
{
    "39.97.63.215:80": 1,
    "39.97.63.216:80": 1
}


# Update the weight of a node to the Upstream
$ curl http://127.0.0.1:9180/apisix/admin/upstreams/100 -H'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PATCH -i -d '
{
    "nodes": {
        "39.97.63.216:80": 10
    }
}'
HTTP/1.1 200 OK
...

After successful execution, nodes will be updated to:
{
    "39.97.63.215:80": 1,
    "39.97.63.216:80": 10
}


# Delete a node for the Upstream
$ curl http://127.0.0.1:9180/apisix/admin/upstreams/100 -H'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PATCH -i -d '
{
    "nodes": {
        "39.97.63.215:80": null
    }
}'
HTTP/1.1 200 OK
...

After successful execution, nodes will be updated to:
{
    "39.97.63.216:80": 10
}


# Replace the nodes of the Upstream
$ curl http://127.0.0.1:9180/apisix/admin/upstreams/100/nodes -H'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PATCH -i -d '
{
    "39.97.63.200:80": 1
}'
HTTP/1.1 200 OK
...

After the execution is successful, nodes will not retain the original data, and the entire update is:
{
    "39.97.63.200:80": 1
}

Response Parameters

Return response from etcd currently.

Back to TOC

SSL

API:/apisix/admin/ssl/{id}

Description:SSL.

Request Methods:

MethodRequest URIRequest BodyDescription
GET/apisix/admin/ssl/{id}NULLFetch resource
PUT/apisix/admin/ssl/{id}{...}Create resource by ID
POST/apisix/admin/ssl{...}Create resource, and ID is generated by server
DELETE/apisix/admin/ssl/{id}NULLRemove resource

Request Body Parameters:

ParameterRequiredTypeDescriptionExample
certTrueCertificatehttps certificate
keyTruePrivate keyhttps private key
certsFalseAn array of certificatewhen you need to configure multiple certificate for the same domain, you can pass extra https certificates (excluding the one given as cert) in this field
keysFalseAn array of private keyhttps private keys. The keys should be paired with certs above
sniTrueMatch Ruleshttps SNI
labelsFalseMatch RulesKey/value pairs to specify attributes{“version”:“v2”,“build”:“16”,“env”:“production”}
create_timeFalseAuxiliaryepoch timestamp in second, will be created automatically if missing1602883670
update_timeFalseAuxiliaryepoch timestamp in second, will be created automatically if missing1602883670

Config Example:

{
    "id": "1",      # id
    "cert": "cert", # Certificate
    "key": "key",   # Private key
    "sni": "sni"    # https SNI
}

Plugin Metadata

API:/apisix/admin/plugin_metadata/{plugin_name}

Description: plugin metadata.

Request Methods:

MethodRequest URIRequest BodyDescription
GET/apisix/admin/plugin_metadata/{plugin_name}NULLFetch resource
PUT/apisix/admin/plugin_metadata/{plugin_name}{...}Create resource by plugin name
DELETE/apisix/admin/plugin_metadata/{plugin_name}NULLRemove resource

Request Body Parameters:

A json object with a data structure defined according to metadata_schema of the plugin ({plugin_name}).

Config Example:

$ curl http://127.0.0.1:9180/apisix/admin/plugin_metadata/example-plugin  -H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -i -X PUT -d '
{
    "skey": "val",
    "ikey": 1
}'
HTTP/1.1 201 Created
Date: Thu, 26 Dec 2019 04:19:34 GMT
Content-Type: text/plain

Back to TOC