Overview
This guide walks through how to create an IPinfo connection and the access it requires to be used in Blink’s Automated Case Management, primarily for Enrichment workflows (IP address geolocation, ASN, and network context lookups).Unlike Microsoft or CrowdStrike, IPinfo does not use OAuth scopes or permission toggles. Access is controlled by a single API token, and the data available is determined by your IPinfo plan tier. See Required Access.
Creating a Connection
IPinfo Connection Guide
Follow this guide to create an IPinfo connection
Required Access
IPinfo has no per-endpoint scope selection. Access is governed by the plan tier of your token, which determines the data depth and request quota available to Blink:Optional: restrict token usage
Optional: restrict token usage
IPinfo supports restricting a token to specific domains or IP addresses. When enabled, requests from any other source are rejected and don’t count toward your usage, which is a useful safeguard for a token used by a backend service. Configure this on the IPinfo API token page.
Which stage of Alert Processing need this connection?
Which stage of Alert Processing need this connection?