VPNDetectionVPNDetection

History

GET
/api/v1/database/downloads

Recent download attempts for this organization, newest first. Refusals are listed too, so a failed transfer can be accounted for.

Authorization

apikey<token>

?apikey=<key>. Convenient in a browser; prefer a header elsewhere.

In: query

Query Parameters

limit?integer

How many attempts to return. Clamped to 1 through 200.

Default50
Range1 <= value <= 200

Response Body

application/json

application/json

curl -X GET "https://api.vpndetection.io/api/v1/database/downloads"
{
  "downloads": [
    {
      "dataset_id": "string",
      "format": "string",
      "outcome": "ok",
      "sample": true,
      "open": true,
      "bytes": 0,
      "http_status": 0,
      "apikey_id": "string",
      "client_ip": "string",
      "user_agent": "string",
      "created": "2019-08-24T14:15:22Z"
    }
  ]
}
{
  "rc": "string"
}

Checksums GET

Checksums for one published file, so a download can be verified after it lands.

Identity GET

The identity behind this credential: what it is, the organization it is scoped to, and the scopes it currently holds. `user` is present for an OAuth token and ABSENT for an API key, which has an organization but no person behind it. `credential.kind` says which you are holding, so a client can branch without guessing from a missing field. Narrower than what the console shows its own user on purpose: an integration needs a name to display and an organization to address, not a profile. The `scopes` array is what the credential may do RIGHT NOW, so a client can render its own capabilities rather than discovering them from a 403.