- Book a call
- Contact us
- Basic
- Advanced
- Live
- Sold
- Market
- General
- Population
- Conditions
- Habitation
Properties
Market Stat
City
GeneralDvfAnalytics - Retrieve advanced statistics of transactions.
API Key used to be authentified to these APIs. Please contact Fluximmo to get one
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.
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/)
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.
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/)
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
Authorizations
API Key used to be authentified to these APIs. Please contact Fluximmo to get one
Body
ANOMALY_UNKNOWN, ANOMALY_OUTLIER, ANOMALY_LOW_PRICE, ANOMALY_HIGH_PRICE, ANOMALY_LOW_SURFACE, ANOMALY_HIGH_SURFACE LOCAL_GROUP_UNKNOWN, LOCAL_GROUP_HOUSE, LOCAL_GROUP_APARTMENT, LOCAL_GROUP_INDUSTRIAL_COMMERCIAL, LOCAL_GROUP_TERRAIN, LOCAL_GROUP_MULTIPLE PROPERTY_TYPE_UNKNOWN, PROPERTY_TYPE_T1, PROPERTY_TYPE_T2, PROPERTY_TYPE_T3, PROPERTY_TYPE_T4, PROPERTY_TYPE_T5, PROPERTY_TYPE_T5_MORE, PROPERTY_TYPE_HOUSE, PROPERTY_TYPE_COMMERCIAL LOCAL_TYPE_UNKNOWN, LOCAL_TYPE_HOUSE, LOCAL_TYPE_APARTMENT, LOCAL_TYPE_INDUSTRIAL_COMMERCIAL, LOCAL_TYPE_DEPENDANCE 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].
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].
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
NATURE_OF_LAND_UNKNOWN, NATURE_OF_LAND_TO_BE_BUILT, NATURE_OF_LAND_PLEASURE_GROUNDS, NATURE_OF_LAND_WOODS, NATURE_OF_LAND_DECIDUOUS_STANDS, NATURE_OF_LAND_MIXED_STANDS, NATURE_OF_LAND_WILLOW_GROVES, NATURE_OF_LAND_POPLAR_GROVES, NATURE_OF_LAND_CONIFEROUS_STANDS, NATURE_OF_LAND_COPPICE_WITH_STANDARDS, NATURE_OF_LAND_SIMPLE_COPPICE, NATURE_OF_LAND_QUARRIES, NATURE_OF_LAND_RAILWAY, NATURE_OF_LAND_WATERS, NATURE_OF_LAND_GARDENS, NATURE_OF_LAND_HEATHS, NATURE_OF_LAND_WOODED_HEATHS, NATURE_OF_LAND_MEADOWS, NATURE_OF_LAND_PASTURES, NATURE_OF_LAND_GRAZING_LAND, NATURE_OF_LAND_FATTENING_MEADOWS, NATURE_OF_LAND_GRASSLANDS, NATURE_OF_LAND_PLANTED_MEADOWS, NATURE_OF_LAND_SOILS, NATURE_OF_LAND_LANDS, NATURE_OF_LAND_PLANTED_LANDS, NATURE_OF_LAND_ORCHARDS, NATURE_OF_LAND_VINEYARDS LOCAL_TYPE_UNKNOWN, LOCAL_TYPE_HOUSE, LOCAL_TYPE_APARTMENT, LOCAL_TYPE_INDUSTRIAL_COMMERCIAL, LOCAL_TYPE_DEPENDANCE PROPERTY_TYPE_UNKNOWN, PROPERTY_TYPE_T1, PROPERTY_TYPE_T2, PROPERTY_TYPE_T3, PROPERTY_TYPE_T4, PROPERTY_TYPE_T5, PROPERTY_TYPE_T5_MORE, PROPERTY_TYPE_HOUSE, PROPERTY_TYPE_COMMERCIAL LOCAL_TYPE_UNKNOWN, LOCAL_TYPE_HOUSE, LOCAL_TYPE_APARTMENT, LOCAL_TYPE_INDUSTRIAL_COMMERCIAL, LOCAL_TYPE_DEPENDANCE PROPERTY_TYPE_UNKNOWN, PROPERTY_TYPE_T1, PROPERTY_TYPE_T2, PROPERTY_TYPE_T3, PROPERTY_TYPE_T4, PROPERTY_TYPE_T5, PROPERTY_TYPE_T5_MORE, PROPERTY_TYPE_HOUSE, PROPERTY_TYPE_COMMERCIAL LOCAL_TYPE_UNKNOWN, LOCAL_TYPE_HOUSE, LOCAL_TYPE_APARTMENT, LOCAL_TYPE_INDUSTRIAL_COMMERCIAL, LOCAL_TYPE_DEPENDANCE 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].
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].
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
MUTATION_NATURE_UNKNOWN, MUTATION_NATURE_SALE, MUTATION_NATURE_SALE_TO_BE_FINNISHED, MUTATION_NATURE_LAND_TO_BUILD, MUTATION_NATURE_EXTENSION, MUTATION_NATURE_EVICTION, MUTATION_NATURE_EXCHANGE UNKNOWN_ANALYZED_TYPE, PRICE_ANALYZED_TYPE, HABITATION_SURFACE_ANALYZED_TYPE, LAND_SURFACE_ANALYZED_TYPE, PRICE_PER_AREA_ANALYZED_TYPE, PRICE_PER_AREA_CARREZ_ANALYZED_TYPE UNKNOWN_ANALYSIS_TYPE, DISTRIBUTION_ANALYSIS_TYPE, SUMMARY_ANALYSIS_TYPE, ADVANCED_ANALYSIS_TYPE, BOX_PLOT_ANALYSIS_TYPE, PERCENTILES_ANALYSIS_TYPE Response
Was this page helpful?