🗺 Ensuring Postal Code gets populated

To whom this may concern:

We have really enjoyed and be benefited greatly from using this API as part of our application. However I do have one improvement/enhancement I would like to suggest.

Below I have a partial response from the /forward route query of Greenwood, Louisiana, USA. Note the postal code is null. Is there anyway in the upgraded subscription or through configuration that I can force all responses to have a postal code?

The reason it matters so much to me is that I have an application that uses Zip code as the primary means of filtering out a result set of over 10,000 potential addresses. My data set is getting working daily but several of our locations do not yet have zip codes. If your API had the means of guaranteeing at least the closest postal code in every response, this would help my application a great deal.

Let me know if you can right away if this is something that can be helped via a higher plan or if there is nothing that can be done. Noticing that postal code more often than not is returned as null today.

{
    "data": [
        {
            "latitude": 32.44293,
            "longitude": -93.97296,
            "type": "locality",
            "name": "Greenwood",
            "number": null,
            "postal_code": null,  
            "street": null,
            "confidence": 0.6,
            "region": "Louisiana",
            "region_code": "LA",
            "county": null,
            "locality": "Greenwood",
            "administrative_area": null,
            "neighbourhood": null,
            "country": "United States",
            "country_code": "USA",
            "continent": "North America",
            "label": "Greenwood, LA, USA"
        },
        {
            "latitude": 30.54491,
            "longitude": -91.10677,
            "type": "locality",
            "name": "Greenwood",
            "number": null,
            "postal_code": null,
            "street": null,
            "confidence": 0.6,
            "region": "Louisiana",
            "region_code": "LA",
            "county": null,
            "locality": "Greenwood",
            "administrative_area": null,
            "neighbourhood": null,
            "country": "United States",
            "country_code": "USA",
            "continent": "North America",
            "label": "Greenwood, LA, USA"
        },
    ]
}

+1, we need this feature too.

Hello Yall, how did you fix this missing postal_code ? on the demo, the postal_code is not empty, it's because i m using a free account maybe.

nope. Ended up using geonames. Even on most expensive plan with promised support position stack never replied

On Wed, Jun 1, 2022, 6:12 AM Nymphea Studio @.***> wrote:

Hello Yall, how did you fix this missing postal_code ? on the demo, the postal_code is not empty, it's because i m using a free account maybe.

— Reply to this email directly, view it on GitHub https://github.com/apilayer/positionstack/issues/2#issuecomment-1143665601, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABWQBAOXQHJVZBIOYFTIKDTVM5VV3ANCNFSM4UKQBOTA . You are receiving this because you commented.Message ID: @.***>