What we shipped this month: geocoding, IP, time zone and more
A roundup of recent work across the API: new compatibility hosts, faster time zone and elevation lookups, dashboard features, and clearer quota visibility.
IP threat and network detail available on request
A location is often only part of what matters about an IP address. Whether that address is associated with known threat activity, and what kind of network it actually belongs to, can matter just as much for fraud prevention, access control, or general risk assessment. /v1/ip now returns exactly that information as an optional extra, available whenever you ask for it.
Adding mg_extras=1 to a request, or sending an X-MG-Extras header, layers IP threat and network detail on top of the standard location response, without changing anything about the base fields already returned. Leave that flag off, and the response is exactly what it always was. Add it, and the same call returns additional detail alongside the location fields you already receive.
This same mechanism applies to ground elevation as well, so mg_extras=1 is a single, consistent way to request additional depth across different endpoints, rather than a separate flag per feature. It also applies across our compatibility hosts, so a request shaped for ip-api.com, ipinfo.io, or ipstack can add the same flag or header on top of its otherwise exactly matched request and response format, gaining threat and network detail without breaking compatibility with the original shape.
Pricing does not change based on whether extras are requested. A lookup with mg_extras=1 added counts as the same single request against your free allowance, prepaid credit, or Unlimited package as a lookup without it. There is no separate, more expensive tier for the additional detail, and no separate quota to track for extras specifically.
This is aimed squarely at use cases where location alone is not enough. An application screening signups for suspicious activity, a service deciding whether to apply extra verification to a given connection, or a security tool building a broader picture of network reputation can all pull that context directly from the same /v1/ip call they are already making, rather than maintaining a second integration with a separate threat intelligence provider just for that one piece.
Full documentation for the IP endpoints, including how to add extras, is available at /docs/ipv4-lookup/ and /docs/ipv6-lookup/. Since it is entirely opt in, testing it against an existing integration is as simple as adding one flag to a call you already make.