What IP addresses does the Context API use?
The Context API is served from api.spur.us over HTTPS on port 443, so the simplest firewall rule is to allow that hostname. If your firewall can only allow IP addresses, allow Spur's fixed addresses: 136.82.115.246 (IPv4) and 2600:1901:0:448b:: (IPv6). api.spur.us used to be served from Google's shared IP addresses, which change. If you allowed those instead of the hostname and Context API requests now time out or can't connect, add the two addresses above. See Network and firewall in the Context API docs: https://docs.spur.us/context-api#network-and-firewall
Similar questions
Why does my API key return a 401 error?
A 401 from the Context API usually means the API key is invalid, expired, or missing from the request. Common causes: the key was rotated or revoked, the key is being sent in the wrong header format, or the subscription has lapsed. Check your API key under Settings → API and confirm your subscription is active before retrying.
Why is my API request failing with a permissions error?
Each API token has specific permissions enabled by an organization admin. If a request fails with a permissions error, an admin can review and update the token's permissions under Settings → API. For historical Context API requests specifically, a permissions error can also mean the account doesn't have the Enterprise historical-access add-on subscription enabled, separate from the token's own permission settings.
How do I get my Context API token?
If you purchased the API from our website or linked your enterprise plan to an online account, view your token at https://app.spur.us/settings/api. Otherwise, contact your Spur rep for access information.
How far back does the Historical Context API go?
The Historical Context API covers approximately the past 2 years of data, available as an add-on subscription on Enterprise plans.
Where can I see my Context API usage and quota?
Open Context API in the Spur app. The dashboard shows Queries Used against your quota, when the current billing period ends, and Queries Today, your daily average and your peak day, with a chart of daily usage. Your quota resets with your billing cycle, and Spur doesn't charge overages: when the quota is used up, the API stops returning data until it resets.
Related guides & explainers
Context API Chrome Extension
Install Spur's Context API Chrome Extension to look up IP enrichment data directly from any web page — highlight an IP and get results inline, without leaving your browser. This is a developer-mode tool, not a Chrome Web Store listing.
What "Client Proxies" Means in Spur Data
"Client Proxies" in Spur data describes proxy-network activity Spur observed coming from an IP — it does not mean the IP is owned or operated by the listed provider.
Why the Organization Field Isn't Available the Same Way Across Spur's Data Feeds
The Context API's per-IP organization field isn't guaranteed in every data feed. Each feed has a different schema and covers a different slice of IP space, so field availability varies by feed.
Entrance IPs vs. Exit IPs for Anonymizing Tunnels
Some anonymizing tunnel configurations route through shared infrastructure, like Cloudflare, before reaching the tunnel operator's own exit point. Here's why blocking the entrance IP can affect unrelated legitimate traffic, and what to enforce on instead.