timestamp1570461300001Incorrect Email Reportsby Ipregistry TeamSome of you may have received an email reporting the wrong number of weekly or monthly request calls to our API. We apologize for the inconvenience. Be reassured, the issue is now fixed and it was only affecting email reports: your...
timestamp1567062900001Error Code for Bad Inputsby Ipregistry TeamIt has been reported that inputting an invalid request body value for the batch lookup endpoint (using the POST method) was returning an HTTP 500 error. This was not impacting the service but confusing users. We have introduced a new...
timestamp1565265600001More Data Points!by Ipregistry TeamIt was awaited by most of you. We've deployed a big update that brings new data points. Thanks to the hard work we made these last weeks to correlate and analyze data, we are proud to announce new data fields! The API is returning a new...
timestamp1564477200001Throttling per Client IPby Ipregistry TeamWe've improved our Rate limit/throttling feature. Once enabled, the rate limit feature was limiting the total number of requests that can be made per hour for a given API key. It was possible to have a user that consumes 10,000 look...
timestamp1560416400001Browser and Device detection 🔍by Ipregistry TeamThe Ipregistry API can now be used to detect any Browser, Device & OS in Real-Time. Here is an example: https://api.ipregistry.co/user_agent?key=tryout In case you need to retrieve this information for the requester along with IP data...
Subscribe to updatesSubscribe to updates