API Authentication
All IPGeolocation.io API endpoints except /v3/getip require authentication. Use an API key for all authenticated endpoints, including bulk requests. Request Origin authentication is available on supported single-lookup endpoints for eligible paid accounts; it does not replace the API key required for bulk requests. The Get IP endpoint does not require authentication.
Your plan determines what you can access (credits and features), but this page focuses on authentication methods and request credentials.
At a Glance
- Recommended for backend/server-side requests: API key using
apiKeyquery parameter. - For browser-based single lookups on paid plans: Request Origin (CORS). Bulk requests always need an API key.
- No-auth utility endpoint:
/v3/getip.
Authentication Methods
IPGeolocation.io supports two authentication methods:
1. API Key (Recommended)
You can make authenticated API requests by passing your API key as a query parameter.
How to Use:
- Log in to your Billing dashboard.
- Copy your API key from the
API Keyssection. - Pass
apiKeyas a query parameter in your requests. - Do not place API keys in client-side JavaScript. For server-side usage, store your API key in environment variables.
Example request with apiKey:
curl -X GET 'https://api.ipgeolocation.io/v3/ipgeo?apiKey=API_KEY&ip=8.8.8.8'I. Database Subscribers (Downloads)
If you are a database subscriber, you also need a valid IPGeolocation.io API key to download and use database archives.
See Databases Documentation for database plans and file details.
2. Request Origin (CORS) (Paid Plans Only)
Request Origin lets you call APIs from client-side JavaScript without exposing your API key in frontend code. This is available on all paid plans for single-lookup endpoints; bulk endpoints always require an API key.
How to Configure:
- Log in to your Billing dashboard.
- In the
API Keyssection, clickAdd moreto add a new API key or request origin. - A form opens with two options:
API KeyandRequest Origin. - Choose
Request Originsand enter the domain where requests will be made. - After saving, requests from the main domain and subdomains work without passing
apiKey.
API Key and Request Origin Limits (By Plan)
The number of extra API keys and request origins is limited based on your plan.
| Plan | No. of Extra API Keys + Request Origins |
|---|---|
| Starter 150K credits/month | 1 |
| Plus 500K credits/month | 2 |
| Pro 1M credits/month | 2 |
| Business 2M credits/month | 3 |
| Premium 5M credits/month | 3 |
Frequently Asked Questions
/v3/getip require authentication. An API key works on every authenticated endpoint, including bulk; Request Origin (CORS) works only for single lookups on paid plans.apiKey as a query parameter in your API requests.