PositionStack drop-in replacement
PositionStack's forward and reverse endpoints answer at positionstack.mygeocode.com with the same data array and flat field names. HTTPS is available on every plan here, including free.
Change one hostname
| Original host |
|
|---|---|
| Use instead | positionstack.mygeocode.com |
| Key parameter | access_key (put your My Geocode key here, or leave it out for the free 2,500 a day) |
curl "http://api.positionstack.com/v1/forward?access_key=YOUR_POSITIONSTACK_KEY&query=350+5th+Avenue+New+York"curl "https://positionstack.mygeocode.com/v1/forward?access_key=YOUR_MYGEOCODE_KEY&query=350+5th+Avenue+New+York"Why people move
PositionStack's free plan is HTTP only and capped monthly. Here everything is HTTPS and the free allowance resets every day.
Try it before you sign up for anything. Requests to positionstack.mygeocode.com count toward the same 2,500 a day you get on our own endpoints, with no key and no account. Above that, credits at $0.001 per request or €50 a month unlimited. Signing up takes an email address and nothing else.
Endpoints
| Path on positionstack.mygeocode.com | What it does | Backed by |
|---|---|---|
/v1/forward?query=... | Forward geocoding | Forward geocoding |
/v1/reverse?query=lat,lng | Reverse geocoding | Reverse geocoding |
Example response
This is what the request above returns. Field names, nesting and types follow PositionStack. Only the data behind them is ours.
{
"data": [
{
"latitude": 40.748428,
"longitude": -73.985654,
"type": "address",
"name": "350 5th Avenue",
"number": "350",
"postal_code": "10118",
"street": "5th Avenue",
"confidence": 1,
"region": "New York",
"region_code": "NY",
"county": "New York County",
"locality": "New York",
"administrative_area": null,
"neighbourhood": "Midtown",
"country": "United States",
"country_code": "USA",
"continent": "North America",
"label": "350 5th Avenue, New York, NY, USA"
}
]
}Details and differences
- country_code is the three-letter code, as PositionStack returns it.
- The country, region, limit, fields, timezone_module and output=xml parameters are honoured, except that xml output is not available.
If your client depends on a field or behaviour that is not listed here, tell us. Compatibility gaps get fixed quickly because they are usually small.