Migrating a Zapier or Make automation to a new geocoding host
No-code automations built on a geocoding step need a different migration approach than custom code does. Here is how to handle that switch.
Migrating from ipinfo.io
ipinfo.io has a distinctive response style: a loc field combining latitude and longitude into a single comma-separated string rather than two separate numbers, and an org field that bundles the autonomous system number and organization name together, something like "AS15169 Google LLC" in one string. Authentication is a token, and the response otherwise stays compact and mostly flat, with fields like city, region, country, and postal alongside those two combined fields.
That combined string formatting is worth flagging specifically, because code that parses loc by splitting on a comma, or parses org by splitting on the first space, is doing real work that has to keep functioning correctly after a migration. It is exactly the kind of small parsing detail that is easy to overlook until a production request returns something the split logic does not expect.
My Geocode's ipinfo compatibility host reproduces this same compact structure, including the combined loc string and the AS-number-prefixed org string, with the copyright, terms, and privacy text being the only content that differs. The reference is at /compatibility/ipinfo/. Parsing logic built around splitting loc and org should keep working exactly as written.
IP lookups are one of the endpoints where real results can be described directly rather than just the shape. A lookup against a given address returns city, region, country, the combined coordinate string, and the combined organization string, live rather than served from a stale cache, since IP geolocation data at My Geocode is kept current with a caching layer that refreshes rather than one that goes stale.
Migration specifics to plan for:
- Token-based authentication maps onto our four supported styles:
X-API-Keyheader,Authorization: Bearerheader, HTTP Basic auth, or a query parameter - Optional extras (IP threat signals, deeper network detail) sit alongside the standard compact shape when requested with
mg_extras=1or anX-MG-Extrasheader, without breaking the fields your code already reads - Quota visibility comes through response headers on every call, including
X-Quota-UsedandX-Credits-Remaining, useful if your current integration tracks usage manually
Pricing: 2,500 free requests a day with no key, another 2,500 free per key per day counted per network, then prepaid credit at €0.0001 per request or an Unlimited key at €50 a month, with every endpoint including this compatibility host priced the same. For applications built around ipinfo's specific compact format for logging, analytics, or access decisions, the goal of this migration is that the format itself never has to change, only what serves it.