API: `GET` data limit

Currently the API can only PUT or DELETE a data limit. This makes it difficult to track the actual data limit being enforced to the server or an access key. We should allow GET on /access-keys/{id}/data-limit and /experimental/access-key-data-limit.

[database64128]

@parsalotfy It’s the path in the API URL. For example, if your API URL is https://example.com/secret, you can GET https://example.com/secret/access-keys to list the access keys.

[JonathanDCohen]

Hey there! Thanks for bringing up the issue. I agree that the API for individual access keys is a bit clunky, but thankfully you don’t need it to get the information you need.

You can currently get the data limit enforced on each key either through the UI

Or using GET /server, which returns a JSON blob looking something like

{
  ...
  "accessKeyDataLimit": {
    "bytes": 5000000000
  },
  ...
}

To get programmatic access to information about individual access keys using the API, you could use something like jq:

$ curl -k https://my.server:address/$PREFIX/access-keys | jq '.accessKeys[] | select(.id == "1")'

{
  "id": "1",
  "name": "Key Name",
  "password": "somePassword",
  "port": 12345,
  "method": "chacha20-ietf-poly1305",
  "accessUrl": "ss://..."
}

We have a Help Article about data limits which might also help you out.