SearchSellers - Give search capabilities to retrieve real-estate sellers. This is suitable for an end-user search experience.
API Key used to be authentified to these APIs. Please contact Fluximmo to get one
Authorizations
API Key used to be authentified to these APIs. Please contact Fluximmo to get one
Body
Shape which has already been stored inside fluximmo services. This is particularly useful for when you have a pre-defined list of shapes and you want to reference the list using a logical name (for example Ile-de-France) rather than having to provide coordinates each time.
UNKNOWN_GEO_INDEX
, DEPARTMENT_GEO_INDEX
, CITY_GEO_INDEX
, REGION_GEO_INDEX
Matches geopoint values within a given distance of a geopoint (pin).
The latitude in degrees. It must be in the range [-90.0, +90.0].
The longitude in degrees. It must be in the range [-180.0, +180.0].
Use a geo_bounding_box filter to match geo_point values that intersect a bounding box. To define the box, provide geopoint values for two opposite corners.
The latitude in degrees. It must be in the range [-90.0, +90.0].
The longitude in degrees. It must be in the range [-180.0, +180.0].
The latitude in degrees. It must be in the range [-90.0, +90.0].
The longitude in degrees. It must be in the range [-180.0, +180.0].
Filter documents indexed using. The behaviour of the GeoShape query depends on the type and relation defined. This have the same specs as the GeoJson RFC 7946 (read more here: https://geojson.org/)
UNKNOWN_SPATIAL_RELATION
, WITHIN
, CONTAINS
, DISJOINT
, INTERSECTS
UNKNOWN_GEO_SHAPE_TYPE
, POINT
, LINE_STRING
, POLYGON
, MULTI_POINT
, MULTI_LINE_STRING
The latitude in degrees. It must be in the range [-90.0, +90.0].
The longitude in degrees. It must be in the range [-180.0, +180.0].
Matches geopoint values within a given distance of a insee code.
Hierarchical Geobased data-representation. This create a grid of the world with a certain level of details depending on the actual picked index. Please see more here: https://h3geo.org/docs/core-library/restable
Shape which has already been stored inside fluximmo services. This is particularly useful for when you have a pre-defined list of shapes and you want to reference the list using a logical name (for example Ile-de-France) rather than having to provide coordinates each time.
UNKNOWN_GEO_INDEX
, DEPARTMENT_GEO_INDEX
, CITY_GEO_INDEX
, REGION_GEO_INDEX
Matches geopoint values within a given distance of a geopoint (pin).
The latitude in degrees. It must be in the range [-90.0, +90.0].
The longitude in degrees. It must be in the range [-180.0, +180.0].
Use a geo_bounding_box filter to match geo_point values that intersect a bounding box. To define the box, provide geopoint values for two opposite corners.
The latitude in degrees. It must be in the range [-90.0, +90.0].
The longitude in degrees. It must be in the range [-180.0, +180.0].
The latitude in degrees. It must be in the range [-90.0, +90.0].
The longitude in degrees. It must be in the range [-180.0, +180.0].
Filter documents indexed using. The behaviour of the GeoShape query depends on the type and relation defined. This have the same specs as the GeoJson RFC 7946 (read more here: https://geojson.org/)
UNKNOWN_SPATIAL_RELATION
, WITHIN
, CONTAINS
, DISJOINT
, INTERSECTS
UNKNOWN_GEO_SHAPE_TYPE
, POINT
, LINE_STRING
, POLYGON
, MULTI_POINT
, MULTI_LINE_STRING
The latitude in degrees. It must be in the range [-90.0, +90.0].
The longitude in degrees. It must be in the range [-180.0, +180.0].
Matches geopoint values within a given distance of a insee code.
Hierarchical Geobased data-representation. This create a grid of the world with a certain level of details depending on the actual picked index. Please see more here: https://h3geo.org/docs/core-library/restable
AFFILIATION_UNKNOWN
, AFFILIATION_FNAIM
, AFFILIATION_AMEPI
, AFFILIATION_SNPI
, AFFILIATION_UNIS
, AFFILIATION_FPI
ORIGIN_UNKNOWN
, ORIGIN_STANDARD
, ORIGIN_FLOW
, ORIGIN_MANUAL
SOURCE_UNKNOWN
, SOURCE_BANO
, SOURCE_OSM
PRECISION_LEVEL_UNKNOWN
, PRECISION_LEVEL_ROOFTOP
, PRECISION_LEVEL_STREET
, PRECISION_LEVEL_CITY
, PRECISION_LEVEL_NOT_FOUND
PLACE_UNKNOWN
, PLACE_STREET
, PLACE_PLACE
, PLACE_CITY
, PLACE_TOWN
, PLACE_VILLAGE
PRECISION_UNKNOWN
, PRECISION_APPROXIMATE
, PRECISION_PARTIAL
, PRECISION_GOOD
, PRECISION_EXACT
, PRECISION_NOT_FOUND
PRECISION_UNKNOWN
, PRECISION_APPROXIMATE
, PRECISION_PARTIAL
, PRECISION_GOOD
, PRECISION_EXACT
, PRECISION_NOT_FOUND
PRECISION_UNKNOWN
, PRECISION_APPROXIMATE
, PRECISION_PARTIAL
, PRECISION_GOOD
, PRECISION_EXACT
, PRECISION_NOT_FOUND
PRECISION_UNKNOWN
, PRECISION_APPROXIMATE
, PRECISION_PARTIAL
, PRECISION_GOOD
, PRECISION_EXACT
, PRECISION_NOT_FOUND
PLACE_UNKNOWN
, PLACE_STREET
, PLACE_PLACE
, PLACE_CITY
, PLACE_TOWN
, PLACE_VILLAGE
Shape which has already been stored inside fluximmo services. This is particularly useful for when you have a pre-defined list of shapes and you want to reference the list using a logical name (for example Ile-de-France) rather than having to provide coordinates each time.
UNKNOWN_GEO_INDEX
, DEPARTMENT_GEO_INDEX
, CITY_GEO_INDEX
, REGION_GEO_INDEX
Matches geopoint values within a given distance of a geopoint (pin).
The latitude in degrees. It must be in the range [-90.0, +90.0].
The longitude in degrees. It must be in the range [-180.0, +180.0].
Use a geo_bounding_box filter to match geo_point values that intersect a bounding box. To define the box, provide geopoint values for two opposite corners.
The latitude in degrees. It must be in the range [-90.0, +90.0].
The longitude in degrees. It must be in the range [-180.0, +180.0].
The latitude in degrees. It must be in the range [-90.0, +90.0].
The longitude in degrees. It must be in the range [-180.0, +180.0].
Filter documents indexed using. The behaviour of the GeoShape query depends on the type and relation defined. This have the same specs as the GeoJson RFC 7946 (read more here: https://geojson.org/)
UNKNOWN_SPATIAL_RELATION
, WITHIN
, CONTAINS
, DISJOINT
, INTERSECTS
UNKNOWN_GEO_SHAPE_TYPE
, POINT
, LINE_STRING
, POLYGON
, MULTI_POINT
, MULTI_LINE_STRING
The latitude in degrees. It must be in the range [-90.0, +90.0].
The longitude in degrees. It must be in the range [-180.0, +180.0].
Matches geopoint values within a given distance of a insee code.
Hierarchical Geobased data-representation. This create a grid of the world with a certain level of details depending on the actual picked index. Please see more here: https://h3geo.org/docs/core-library/restable
Shape which has already been stored inside fluximmo services. This is particularly useful for when you have a pre-defined list of shapes and you want to reference the list using a logical name (for example Ile-de-France) rather than having to provide coordinates each time.
UNKNOWN_GEO_INDEX
, DEPARTMENT_GEO_INDEX
, CITY_GEO_INDEX
, REGION_GEO_INDEX
Matches geopoint values within a given distance of a geopoint (pin).
The latitude in degrees. It must be in the range [-90.0, +90.0].
The longitude in degrees. It must be in the range [-180.0, +180.0].
Use a geo_bounding_box filter to match geo_point values that intersect a bounding box. To define the box, provide geopoint values for two opposite corners.
The latitude in degrees. It must be in the range [-90.0, +90.0].
The longitude in degrees. It must be in the range [-180.0, +180.0].
The latitude in degrees. It must be in the range [-90.0, +90.0].
The longitude in degrees. It must be in the range [-180.0, +180.0].
Filter documents indexed using. The behaviour of the GeoShape query depends on the type and relation defined. This have the same specs as the GeoJson RFC 7946 (read more here: https://geojson.org/)
UNKNOWN_SPATIAL_RELATION
, WITHIN
, CONTAINS
, DISJOINT
, INTERSECTS
UNKNOWN_GEO_SHAPE_TYPE
, POINT
, LINE_STRING
, POLYGON
, MULTI_POINT
, MULTI_LINE_STRING
The latitude in degrees. It must be in the range [-90.0, +90.0].
The longitude in degrees. It must be in the range [-180.0, +180.0].
Matches geopoint values within a given distance of a insee code.
Hierarchical Geobased data-representation. This create a grid of the world with a certain level of details depending on the actual picked index. Please see more here: https://h3geo.org/docs/core-library/restable
Hierarchical Geobased data-representation. This create a grid of the world with a certain level of details depending on the actual picked index. Please see more here: https://h3geo.org/docs/core-library/restable
Hierarchical Geobased data-representation. This create a grid of the world with a certain level of details depending on the actual picked index. Please see more here: https://h3geo.org/docs/core-library/restable
SELLER_TYPE_UNKNOWN
, SELLER_TYPE_AGENCY
, SELLER_TYPE_NETWORK
RELEVANCE
, AGENCY_CREATION_AT
, AGENCY_MODIFIED_AT
, REVIEW_SCORE
, INDEXED_AT
ASC
, DESC
Response
SELLER_TYPE_UNKNOWN
, SELLER_TYPE_AGENCY
, SELLER_TYPE_NETWORK
Hierarchical Geobased data-representation. This create a grid of the world with a certain level of details depending on the actual picked index. Please see more here: https://h3geo.org/docs/core-library/restable
Hierarchical Geobased data-representation. This create a grid of the world with a certain level of details depending on the actual picked index. Please see more here: https://h3geo.org/docs/core-library/restable
AFFILIATION_UNKNOWN
, AFFILIATION_FNAIM
, AFFILIATION_AMEPI
, AFFILIATION_SNPI
, AFFILIATION_UNIS
, AFFILIATION_FPI
ORIGIN_UNKNOWN
, ORIGIN_STANDARD
, ORIGIN_FLOW
, ORIGIN_MANUAL
SOURCE_UNKNOWN
, SOURCE_BANO
, SOURCE_OSM
PRECISION_LEVEL_UNKNOWN
, PRECISION_LEVEL_ROOFTOP
, PRECISION_LEVEL_STREET
, PRECISION_LEVEL_CITY
, PRECISION_LEVEL_NOT_FOUND
PLACE_UNKNOWN
, PLACE_STREET
, PLACE_PLACE
, PLACE_CITY
, PLACE_TOWN
, PLACE_VILLAGE
PRECISION_UNKNOWN
, PRECISION_APPROXIMATE
, PRECISION_PARTIAL
, PRECISION_GOOD
, PRECISION_EXACT
, PRECISION_NOT_FOUND
PRECISION_UNKNOWN
, PRECISION_APPROXIMATE
, PRECISION_PARTIAL
, PRECISION_GOOD
, PRECISION_EXACT
, PRECISION_NOT_FOUND
PRECISION_UNKNOWN
, PRECISION_APPROXIMATE
, PRECISION_PARTIAL
, PRECISION_GOOD
, PRECISION_EXACT
, PRECISION_NOT_FOUND
PRECISION_UNKNOWN
, PRECISION_APPROXIMATE
, PRECISION_PARTIAL
, PRECISION_GOOD
, PRECISION_EXACT
, PRECISION_NOT_FOUND
PLACE_UNKNOWN
, PLACE_STREET
, PLACE_PLACE
, PLACE_CITY
, PLACE_TOWN
, PLACE_VILLAGE
Hierarchical Geobased data-representation. This create a grid of the world with a certain level of details depending on the actual picked index. Please see more here: https://h3geo.org/docs/core-library/restable
Hierarchical Geobased data-representation. This create a grid of the world with a certain level of details depending on the actual picked index. Please see more here: https://h3geo.org/docs/core-library/restable
Hierarchical Geobased data-representation. This create a grid of the world with a certain level of details depending on the actual picked index. Please see more here: https://h3geo.org/docs/core-library/restable
Hierarchical Geobased data-representation. This create a grid of the world with a certain level of details depending on the actual picked index. Please see more here: https://h3geo.org/docs/core-library/restable
Was this page helpful?