Skip to main content
POST
Send a JSON body containing one IPv4 or IPv6 address. The response always includes the seven documented data fields, but any individual value can be null when the selected provider has no matching information.
Live Testing Guide: Before using Try it, create a Development project, then enter its Client ID and Client Secret. Configure the relevant provider for that project before sending the request.

API endpoint

POST

Request fields

Outside the documentation Playground, do not use a raw client-side IP collection flow just to call this API from a browser. Keep the API secret on your backend and send the lookup from there.

Result fields

meta.provider_override mirrors the optional provider hint sent in the request. It is not a guarantee that a particular provider produced every field.

Request example

This example uses IPv4. The same ip field also accepts a valid IPv6 address, such as 2001:4860:4860::8888.
curl
Use only an IP address that you are permitted to process. Provider data is address-dependent, so an IPv4 or IPv6 lookup can legitimately return null for one or more result fields.

Response example

Error codes

Keep the JSON request_id or X-APIX-Request-ID response header with your support record. It is the safest way for AvraAPI support to trace a request without asking for the original IP address.
See the REST API guide for shared credential, privacy, and error-handling guidance.

Playground resources

The generated reference below lists this endpoint’s API standard details: request fields, authorizations, and response schema. The complete integration guide, request and response examples, and endpoint-specific error handling are above.

Authorizations

X-API-KEY
string
header
required

Your Development project's Client ID. Enter your own value in the Documentation Playground.

X-API-SECRET
string
header
required

Your Development project's Client Secret. Mintlify does not proxy these requests; the browser sends them directly to AvraAPI. Never enter a Production secret in the Documentation Playground.

Headers

X-ENV
enum<string>
default:development

Selects the Development credential environment. The Documentation Playground exposes Development values only; normal backend integrations may use their documented Production credentials outside this tool.

Available options:
dev,
development
Accept
string

Requests a JSON response where the selected operation supports JSON.

Example:

"application/json"

X-Privacy-Mode
boolean
default:false

Optional privacy override. Turn this on to request that AvraAPI suppress request-payload storage in observability logs for this request.

Example:

true

Body

application/json
ip
string<ip>
required

A valid IPv4 or IPv6 address without leading or trailing whitespace.

Example:

"203.0.113.10"

provider
string | null

Optional provider hint. Omit it to use the project's primary enabled Location provider. maxmind is the currently supported explicit value.

Maximum string length: 50
Pattern: ^[A-Za-z0-9_-]+$
Example:

"maxmind"

Response

Location result. Every field in data is present and may be null.

success
enum<boolean>
required
Available options:
true
request_id
string<uuid>
required

Include this value when contacting AvraAPI support.

data
object
required

Operation-specific result data.

meta
object
required
Last modified on October 1, 2026