Due to the imperfections of any GeoIP service, I decided to create one that gathers information from all available free GeoIP services I could find, and makes decision through voting.
Because of the data discrepancies among these free GeoIP services, my service can only provide ‘country’ and ‘country_code’ information.
All data received from GeoIP services is cached for 7 days, so repeated requests will be processed much faster than the first one. However, you can bypass the 7-day results cache by adding the ‘force_update’ parameter.
Returns data in JSON format.
Most powerful endpoint.
Object | Description |
---|---|
ip |
[Required] IPv4 or IPv6 address. Note that not every GeoIP service supports IPv6, so there will be fewer providers in the voting. |
field |
[Optional] Fields to return (country, country_code, etc.). You can use multiple field parameters: &field=country&field=country_code. If no field parameter is added, it returns all available fields. |
force_update |
[Optional] Bypass the 7-day results cache. |
timeout |
[Optional] Timeout in seconds - limits requests to GeoIP APIs. Helps to improve response time. |
{
"ip": "8.8.4.4",
"country_code": "US",
"country": "United States",
"precision": 1,
"providers_responsed": 21,
"providers_total": 21,
"data_updated": "2024-03-15 22:36:29.381052",
"data": {
"ipapi.co": "US",
"ipinfo.io": "US",
"ip-api.com": "US",
"geojs.io": "US",
"reallyfreegeoip.org": "US",
"ipwho.is": "US",
"country.is": "US",
"geoiplookup.io": "US",
"db-ip.com": "US",
"freeip2geo.net": "US",
"abstractapi.com": "US",
"ipdata.co": "US",
"ipgeolocation.io": "US",
"findip.net": "US",
"extreme-ip-lookup.com": "US",
"snoopi.io": "US",
"ip2location.io": "US",
"api-bdc.net": "US",
"getgeoapi.com": "US",
"ipxplorer.com": "US",
"techniknews.net": "US"
}
}
curl --location --request GET 'https://zylalabs.com/api/3680/geoip+hub+api/4154/json?ip=8.8.4.4' --header 'Authorization: Bearer YOUR_API_KEY'
Returns data in plain text format.
Object | Description |
---|---|
ip |
[Required] IPv4 or IPv6 address. Note that not every GeoIP service supports IPv6, so there will be fewer providers in the voting. |
field |
[Optional] Fields to return (country, country_code, etc.). If no field parameter is added, it returns 'country' field. |
force_update |
[Optional] Bypass the 7-day results cache. |
timeout |
[Optional] Timeout in seconds - limits requests to GeoIP APIs. Helps to improve response time. |
United States
curl --location --request GET 'https://zylalabs.com/api/3680/geoip+hub+api/4155/plain?ip=8.8.4.4' --header 'Authorization: Bearer YOUR_API_KEY'
After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the GeoIP HUB API REST API, simply include your bearer token in the Authorization header.
Header | Description |
---|---|
Authorization
|
[Required] Should be Bearer access_key . See "Your API Access Key" above when you are subscribed. |
No long term commitments. One click upgrade/downgrade or cancellation. No questions asked.
Yes, it is.
Country (United States) and country code (US)
Yes, but remember that not every GeoIP service supports IPv6, so there will be fewer providers in the voting.
Yes, for 7 days. However, you can bypass the 7-day results cache by adding the βforce_updateβ parameter.
Yes, You can use multiple field parameters: &field=country&field=country_code. If no field parameter is added, it returns all available fields.
Zyla API Hub is, in other words, an API MarketPlace. An all-in-one solution for your developing needs. You will be accessing our extended list of APIs with only your user. Also, you won't need to worry about storing API keys, only one API key for all our products is needed.
Prices are listed in USD. We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the worldβs most reliable payment companies. If you have any trouble with paying by card, just contact us at [email protected]
Sometimes depending on the bank's fraud protection settings, a bank will decline the validation charge we make when we attempt to be sure a card is valid. We recommend first contacting your bank to see if they are blocking our charges. If more help is needed, please contact [email protected] and our team will investigate further
Prices are based on a recurring monthly subscription depending on the plan selected β plus overage fees applied when a developer exceeds a planβs quota limits. In this example, you'll see the base plan amount as well as a quota limit of API requests. Be sure to notice the overage fee because you will be charged for each additional request.
Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.
Just go to the pricing page of that API and select the plan that you want to upgrade to. You will only be charged the full amount of that plan, but you will be enjoying the features that the plan offers right away.
Yes, absolutely. If you want to cancel your plan, simply go to your account and cancel on the Billing page. Upgrades, downgrades, and cancellations are immediate.
You can contact us through our chat channel to receive immediate assistance. We are always online from 9 am to 6 pm (GMT+1). If you reach us after that time, we will be in contact when we are back. Also you can contact us via email to [email protected]
Service Level:
100%
Response Time:
652ms
Service Level:
100%
Response Time:
1,074ms
Service Level:
100%
Response Time:
987ms
Service Level:
100%
Response Time:
525ms
Service Level:
100%
Response Time:
1,328ms
Service Level:
100%
Response Time:
866ms
Service Level:
100%
Response Time:
1,161ms
Service Level:
100%
Response Time:
595ms
Service Level:
100%
Response Time:
320ms
Service Level:
100%
Response Time:
696ms
Service Level:
100%
Response Time:
464ms
Service Level:
100%
Response Time:
452ms
Service Level:
100%
Response Time:
1,016ms
Service Level:
100%
Response Time:
865ms
Service Level:
100%
Response Time:
4,313ms
Service Level:
100%
Response Time:
1,026ms
Service Level:
100%
Response Time:
447ms