Using the Typeahead API v1
This is documentation for the Regrid Typeahead API, a separate endpoint that couples nicely with our Parcel API. Please see the Using the API document for full reference on the Parcel API.
The endpoint is accessible via GET requests at:
token: Your Regrid assigned authorization token.
query: A street address or partial address, starting at the beginning
You'll receive a JSON array of matching results like the following. Note this is a lighter-weight format than our regular Parcel API and includes a few essential fields for display and/or further queries to the API.
address: The address
ll_uuid: Our unique parcel identifier, which can be used for more detailed lookups.
score: A confidence score in the match quality between 0.0 and 1.0.
context: The city and state where this parcel was found.
path: The unique parcel "path" that can be used for API lookups or on the web (e.g. https://app.regrid.com/us/mi/wayne/detroit/181893 using the above)
centroid: A lat-long pair of the parcel centroid. Note that this is in
This is designed to accept natural input the way a user might type into a search box, including appending a city, state, or ZIP code to the query. We try our best to parse it intelligently and return meaningful results in real time. These would be acceptable queries
"407 e fort detroit"
"407 e fort detroit mi"
"407 e fort 48226"
Integrating the Typeahead API into your app
We suggest connecting your UI search widget directly to our API endpoints for the most responsive experience as users type an address.
Fetching complete parcel record details
We send a lightweight JSON response in the Typeahead API, including enough information to display results and allow a more complete lookup. To retrieve the full set of data fields for a parcel record, including geometry, please use our Parcel API to look up a record by ll_uuid, using a UUID chosen from the typeahead response.
Here is a sample snippet using the typeahead.js library initially developed by Twitter. It supports search-as-you-type, displaying matches in a dropdown menu, and taking an action when a result is selected.
Notes for client implementation
There are two types of addresses that get loaded, one with address without city, state and zip and a complete address with city, state and zip. We use two sources for the address and provide all options. They are sorted by most relevant to what is entered in the query. The ll_uuid for the address is still the same but this gives the user the flexibility to choose which format to ingest. This also helps when a parcel address has multiple units or secondary addresses.