# SearchAddressByBearerToken Search for an address __Activity name :__ GetSearchAddressByBearerToken Use fuzzy search to find an address. The response returns the GEO coördinates that can be used to calculate a route. This is a read-only table function. The Loket.nl REST API may not support changing the data, or the Invantive UniversalSQL driver for Loket.nl REST does not support it. In the latter case, use the table NativePlatformScalarRequests to upload data to the Loket.nl REST API. - Catalog: `LoketNlRest` - Schema: `LocationService` ## Parameters of Table Function | Name | Data Type | Required | Default Value | Documentation | |---|:---:|:---:|:---:|---| | `lat` | `double` | ☐ | | latitude for the bias in the search results. Results will be ordered in likelyhood to be relevant to the given latitude (and longitude) | | `lon` | `double` | ☐ | | longitude for the bias in the search results. Results will be ordered in likelyhood to be relevant to the given longitude (and latitude) | | `query` | `string` | ☑ | | A term by wich the address might be found the more detailed the better the search results | | `top` | `int32` | ☐ | | the top x number of results that are returned. If not supplied 5 results are returned | ## Columns The columns of the table `SearchAddressByBearerToken` are shown below. Each column has an SQL data type. | Name | Data Type | Label | Required | Documentation | |---|:---:|---|:---:|---| | `address_countryCode` | `string` | | ☐ | isocode of the country | | `address_freeformAddress` | `string(1000)` | | ☐ | description of the address | | `pointOfInterest_name` | `string` | | ☐ | The name of the point of interest | | `position_latitude` | `double` | | ☐ | latitude for the address | | `position_longitude` | `double` | | ☐ | longitude for the address |