SearchAddressByBearerToken: Loket.nl REST itgen_loketnl_searchaddressbybearertoken_plural
read only REST
- Catalog:
LoketNlRest - Schema:
LocationService - Label: itgen_loketnl_searchaddressbybearertoken_plural
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.
Can only retrieve data.
API Source
- Endpoint:
/address/search - Operation:
get /address/search
Parameters
| Name | Data Type | Required | Default | Documentation |
|---|---|---|---|---|
lat |
`` | latitude for the bias in the search results. Results will be ordered in likelyhood to be relevant to the given latitude (and longitude) | ||
lon |
`` | longitude for the bias in the search results. Results will be ordered in likelyhood to be relevant to the given longitude (and latitude) | ||
query |
`` | A term by wich the address might be found the more detailed the better the search results | ||
top |
`` | the top x number of results that are returned. If not supplied 5 results are returned |
Table Columns
The columns of the table SearchAddressByBearerToken are shown below. Each column has an SQL data type. A new non-null value must be provided for every required column at all times during insert and update.
| Name | Data Type | Label | Required | Marks | Documentation |
|---|---|---|---|---|---|
address_ |
varchar2 |
itgen_loketnl_address_countrycode | isocode of the country | ||
address_ |
varchar2 |
itgen_loketnl_address_freeformaddress | description of the address | ||
point |
varchar2 |
itgen_loketnl_pointofinterest_name | The name of the point of interest | ||
position_ |
double |
itgen_loketnl_position_latitude | latitude for the address | ||
position_ |
double |
itgen_loketnl_position_longitude | longitude for the address |
Release Notes
What changed per release in the tables, columns, attributes and capabilities of the driver: