Can anyone advise? My payloads don’t seem to be malformed in any way, unless I am missing something?

Questions & Help
1

Can anyone advise? My payloads don’t seem to be malformed in any way, unless I am missing something?

2

@John_Votta_SafeGraph

3

Upon further investigation, I am noticing a few things:

  1. I’ve narrowed down some test cases which work and don’t work. For example, if I request 400 Jefferson St, York, SC 29745, the API hangs and errors out. On the other hand, if I request 400 W Jefferson St, York, SC 29745 (including street direction), the api successfully returns a placekey. So the API is currently not handling invalid addresses correctly, and failing rather than returning an Invalid address message.
  2. Regarding the Python package: there seem to be some versioning issues with JSON decoding. When I make a bulk api request containing valid addresses using Python 3.8, I get a successful response. On the other hand, when I use Python 3.7 and the exact same request, I get a JSONDecodeError
4

Have you tried setting options.strict_address_match to false?

5

that should be the default setting - Placekey API Docs

6

that link is to an example query, but I don’t believe it actually explicitly says false is the default. perhaps false is the default in the python package. I always set it explicitly in my requests

7

@Alex_Caruso_Entera quick update here:

We’ve identified an issue in the Placekey API which is causing the system to timeout on some invalid addresses. We’ve been experiencing higher loads than average over the past week and believe this is a contributing factor. We are currently working on resolving by attempting to scale our resources along with a couple of other potential fixes - we will provide an update once we have a fix, hopefully within a day or two.