REST APIReference
Discovery
GET
One row per URL section, with its provider count and the category ids that publish under it. section or a category id is what the category parameter elsewhere takes.
header
X-Api-Key<token>A key from POST /keys, starting igk_. Never send it in the URL.
Categories, largest first.
application/json- response
data*array<>curl -X GET 'https://inetgeek.com/api/v1/categories'Example Response
{ "data": [ { "section": "analytics", "provider_count": 0, "category_ids": [ "string" ], "url": "http://example.com" } ]}GET
Every fact key with its human label. Pass keys to /providers?has=.
header
X-Api-Key<token>A key from POST /keys, starting igk_. Never send it in the URL.
Fact keys.
application/json- response
data*array<>curl -X GET 'https://inetgeek.com/api/v1/facts'Example Response
{ "data": [ { "key": "string", "label": "string" } ]}GET
Providers, comparisons, DNS records, tools and stacks. Everyday words for a capability are widened to the words the fact labels use, and matched_criteria names documented facts your terms match, which /providers?has= can then list.
header
X-Api-Key<token>A key from POST /keys, starting igk_. Never send it in the URL.
q*stringFree text, up to 200 characters.
Length
length <= 200Ranked matches.
application/json- response
data*array<>matched_criteria?array<>also_searched?array<string>terms_not_found?array<string>curl -X GET 'https://inetgeek.com/api/v1/search?q=revenue+attribution'Example Response
{ "data": [ { "title": "string", "kind": "string", "url": "http://example.com", "description": "string" } ], "matched_criteria": [ { "key": "string", "label": "string" } ], "also_searched": [ "string" ], "terms_not_found": [ "string" ]}