By default, Nash validates an address on every request when passed a pickup or dropoff address or Google Place ID. When provided with a raw address, Nash uses several geocoding services and selects the most appropriate result based on the region of the address. Once geocoded, Nash will populate the componentized pickup/dropoff address in the corresponding component fields, which will be returned in the API response, providing you with structured and standardized address data.

​
Bypassing Nash’s Address Validation

If you prefer to use your own geocoding service, you can bypass Nash’s address validation by passing the componentized address fields directly. To do this, provide the following fields INSTEAD of the <pickup|dropoff>Address or <pickup|dropoff>PlaceId when creating or updating an order. Pickup
  • pickupAddressNumber
  • pickupAddressSecondaryNumber
  • pickupAddressFormattedStreet*
  • pickupAddressCity*
  • pickupAddressCounty
  • pickupAddressState
  • pickupAddressZip*
  • pickupAddressCountry*
  • pickupLat*
  • pickupLng*
Dropoff
  • dropoffAddressNumber
  • dropoffAddressSecondaryNumber
  • dropoffAddressFormattedStreet*
  • dropoffAddressCity*
  • dropoffAddressCounty
  • dropoffAddressState
  • dropoffAddressZip*
  • dropoffAddressCountry*
  • dropoffLat*
  • dropoffLng*
* = Required components of the address if using address components
When using componentized address fields, do not pass <pickup|dropoff>Address or <pickup|dropoff>PlaceId in the request to create or update an order.

​
Using a Store Location as a Pickup or Dropoff Point

As an alternative to providing an address, address components, or a Google Place ID, you can specify a store location as the pickup or dropoff point for an order. To do this, simply pass the Store Location ID (starting with stl_) or the Store Location External ID in the request when creating or updating an order. When a Store Location ID or External ID is provided without any accompanying address information, Nash will automatically populate the pickup or dropoff address fields using the address associated with the specified store location. This eliminates the need to manually input the address details for frequently used store locations.
If a Store Location ID or External ID is provided along with address information, the address information (including name, phone-number, email, instructions) will take precedence over the store location’s address.