Network & DNS
/api/v1/my-ipPacketFlo What Is My IP Address API
The public IP address PacketFlo sees for your request, and whether it is IPv4 or IPv6. Nothing else: no lookups, so it is the cheapest and fastest endpoint.
Example request
curl "https://packetflo.io/api/v1/my-ip?api_key=YOUR_API_KEY"
Example response
{ "ok": true, "data": { "ip": "203.0.113.42", "version": "IPv4" }, "meta": { "tool": "my-ip", "version": "v1" } }
Reading the result
Returns the public source address observed for this request, without geographic or ownership enrichment.
Response fields
| Field | What it tells you |
|---|---|
ip | Your request's public egress address. A VPN, proxy or shared NAT may appear instead of a device-specific address. |
version | IPv4 or IPv6, based on the connection used for this request. |
Scope and limits
A single request reveals one address family, not both. Use curl -4 or curl -6 to select a family when supported by your network. Trusted proxy configuration determines how the original client address is recovered. Use IP Info for location and network ownership; this endpoint is useful for checking egress addresses and allowlists. Missing or non-public addresses return an API error.
Authentication and errors
Send your key in the x-api-key header, or the supported api_key query parameter. Each request uses 1 credit from the key's shared 300-credit rolling 24-hour budget. Credits are charged before parameter validation. Successful responses and quota errors include usage headers; GET and OPTIONS support CORS.
| API status | Meaning |
|---|---|
200 | The diagnostic returned a result in data, with ok: true and version information in meta. Read the diagnostic fields to determine the target's condition. |
400 | Invalid or blocked input, or a lookup/check failure that could not be returned as a diagnostic result. Read error for details. |
401 | Missing, invalid or revoked API key. |
429 | The request would exceed the key's available credit budget. |