InternetData
Database v2

Checksums

GET
/api/v2/database/checksum

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

Authorization

apikey<token>

?apikey=<key>. Convenient in a browser or a curl one-liner, which is how a database is usually fetched; prefer a header elsewhere.

This is the same v2 key as the other two schemes. A v1 credential is a different vocabulary and fails validation here, as it would anywhere.

In: query

Query Parameters

id*string

Database identifier (e.g. vpn_ip_v1, resproxy_provider_v1).

Match^[a-zA-Z0-9_]+$
format*string

Database file format.

Value in"csvgz" | "mmdb"

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

curl -X GET "https://internetdata.io/api/v2/database/checksum?id=vpn_ip_v1&format=mmdb"
{
  "id": "string",
  "format": "csvgz",
  "checksums": {
    "md5": "string",
    "sha1": "string",
    "sha256": "string",
    "sha512": "string"
  }
}
{
  "rc": "string"
}
{
  "rc": "string"
}
{
  "rc": "string"
}
{
  "rc": "string"
}
{
  "rc": "string"
}

Metadata GET

Poll this to decide whether today's build is worth fetching: it carries `updated` and `entries` without downloading anything. No `format` parameter - one document describes every format the database is built in.

History GET

Refusals are listed too: a denial is what answers "it stopped working", and its absence answers nothing.