BulkAdsAlerts - Create multiple ads alert at the same time to lower the number of calls.
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
OFFER_UNKNOWN
, OFFER_BUY
, OFFER_RENT
, OFFER_BUSINESS_TAKE_OVER
, OFFER_LEASE_BACK
, OFFER_LIFE_ANNUITY_SALE
, OFFER_HOLIDAYS
CLASS_UNKNOWN
, CLASS_HOUSE
, CLASS_FLAT
, CLASS_PROGRAM
, CLASS_SHOP
, CLASS_PREMISES
, CLASS_OFFICE
, CLASS_LAND
, CLASS_BUILDING
, CLASS_PARKING
PROCESS_UNKNOWN
, PROCESS_AVAILABLE_ON_MARKET
, PROCESS_UNDER_COMPROMISE
, PROCESS_RENTED_SOLD
, PROCESS_REMOVED
, PROCESS_RESERVED
, PROCESS_ARCHIVED
PRICING_ONE_OFF
, PRICING_MENSUAL
CURRENCY_EUR
, CURRENCY_USD
PROPERTY_TYPE_UNKNOWN
, PROPERTY_TYPE_STUDIO
, PROPERTY_TYPE_T1
, PROPERTY_TYPE_T1_T2
, PROPERTY_TYPE_T2
, PROPERTY_TYPE_T2_T3
, PROPERTY_TYPE_T3
, PROPERTY_TYPE_T3_4
, PROPERTY_TYPE_T4
, PROPERTY_TYPE_T4_5
, PROPERTY_TYPE_T5_MORE
, PROPERTY_TYPE_LOFT
, PROPERTY_TYPE_DUPLEX
, PROPERTY_TYPE_INDIVIDUAL
, PROPERTY_TYPE_TRADITIONAL
, PROPERTY_TYPE_CONTEMPORARY
, PROPERTY_TYPE_BOURGEOIS
, PROPERTY_TYPE_VILLA
, PROPERTY_TYPE_MANOR
, PROPERTY_TYPE_CASTLE
, PROPERTY_TYPE_FARM
, PROPERTY_TYPE_MAS
, PROPERTY_TYPE_BASTIDE
, PROPERTY_TYPE_CHALET
, PROPERTY_TYPE_ANCIENT
, PROPERTY_TYPE_HERITAGE_LISTED
, PROPERTY_TYPE_BUNGALOW
, PROPERTY_TYPE_STUDETTE
ROOM_TYPE_UNKNOWN
, ROOM_TYPE_MASTER_BEDROOM
, ROOM_TYPE_BEDROOM
, ROOM_TYPE_KITCHEN
, ROOM_TYPE_LIVING_ROOM
, ROOM_TYPE_OFFICE
HEAT_TYPE_UNKNOWN
, HEAT_TYPE_INDIVIDUAL
, HEAT_TYPE_SHARED
, HEAT_TYPE_MIXED
, HEAT_TYPE_CITY
, HEAT_TYPE_CISTERN
HEAT_DETAIL_UNKNOWN
, HEAT_DETAIL_FLOOR
, HEAT_DETAIL_CEILING
, HEAT_DETAIL_FIREPLACE
, HEAT_DETAIL_INSERT
, HEAT_DETAIL_AIR_CON
, HEAT_DETAIL_RADIANTS_TUBES
, HEAT_DETAIL_RADIATOR
, HEAT_DETAIL_SHEATHS
, HEAT_DETAIL_CONVECTOR
HEATING_UNKNOWN
, HEATING_FUEL_OIL
, HEATING_ELECTRICAL
, HEATING_GAS
, HEATING_BIOMASS
, HEATING_SOLAR
, HEATING_GEOTHERMAL
, HEATING_WOOD
, HEATING_HEAT_PUMP
, HEATING_PELLET
, HEATING_CANADIAN_WELL
, HEATING_COAL
KITCHEN_UNKNOWN_EQUIPPED
, KITCHEN_NON_EQUIPPED
, KITCHEN_PARTIALLY_EQUIPPED
, KITCHEN_FULLY_EQUIPPED
, KITCHEN_FURNISHED
, KITCHEN_NAKED
, KITCHEN_EQUIPPED_FURNISHED
VIEW_TYPE_UNKNOWN
, VIEW_TYPE_GLIMPSE
, VIEW_TYPE_PANORAMIC
, VIEW_TYPE_CLEAR
, VIEW_TYPE_EXCEPTIONAL
, VIEW_TYPE_DOMINANT
EXPOSURE_UNKNOWN
, EXPOSURE_NORTH
, EXPOSURE_NORTH_EAST
, EXPOSURE_EAST
, EXPOSURE_SOUTH_EAST
, EXPOSURE_SOUTH
, EXPOSURE_SOUTH_WEST
, EXPOSURE_WEST
, EXPOSURE_NORTH_WEST
UNKNOWN_FURNITURE
, UNFURNISHED
, PARTIALLY_FURNISHED
, FULLY_FURNISHED
MATERIAL_UNKNOWN
, MATERIAL_WOODEN
, MATERIAL_STEEL
, MATERIAL_STONE
, MATERIAL_PVC
, MATERIAL_CONCRETE
, MATERIAL_ALUMINIUM
, MATERIAL_HALF_TIMBERED
, MATERIAL_MARBLE
, MATERIAL_BRICK
, MATERIAL_CINDER_BLOCK
, MATERIAL_PREFABRICATED
, MATERIAL_ADOBE
, MATERIAL_COATING
VIEW_ON_UNKNOWN
, VIEW_ON_SEA
, VIEW_ON_HILLS
, VIEW_ON_RIVERS
, VIEW_ON_CITY
, VIEW_ON_PARK
, VIEW_ON_VERDURE
, VIEW_ON_STREET
, VIEW_ON_COURTYARD
, VIEW_ON_COUNTRYSIDE
, VIEW_ON_MOUNTAIN
, VIEW_ON_GARDEN_TERRACE
, VIEW_ON_LAKE
, VIEW_ON_SKI_SLOPES
, VIEW_ON_PORT
, VIEW_ON_POI
, VIEW_ON_SKY
, VIEW_ON_WATER
, VIEW_ON_VINEYARD
, VIEW_ON_ROOF
GLAZING_TYPE_UNKNOWN
, GLAZING_TYPE_SIMPLE
, GLAZING_TYPE_DOUBLE
, GLAZING_TYPE_TRIPLE
ENERGY_CLASSIFICATION_UNKNOWN
, ENERGY_CLASSIFICATION_G
, ENERGY_CLASSIFICATION_F
, ENERGY_CLASSIFICATION_E
, ENERGY_CLASSIFICATION_D
, ENERGY_CLASSIFICATION_C
, ENERGY_CLASSIFICATION_B
, ENERGY_CLASSIFICATION_A
, ENERGY_CLASSIFICATION_NC
GREENHOUSE_CLASSIFICATION_UNKNOWN
, GREENHOUSE_CLASSIFICATION_G
, GREENHOUSE_CLASSIFICATION_F
, GREENHOUSE_CLASSIFICATION_E
, GREENHOUSE_CLASSIFICATION_D
, GREENHOUSE_CLASSIFICATION_C
, GREENHOUSE_CLASSIFICATION_B
, GREENHOUSE_CLASSIFICATION_A
, GREENHOUSE_CLASSIFICATION_NC
INTERIOR_CONDITION_UNKNOWN
, INTERIOR_CONDITION_EXCELLENT
, INTERIOR_CONDITION_TO_REFRESH
, INTERIOR_CONDITION_SMALL_WORKS_TO_BE_PLANNED
, INTERIOR_CONDITION_MAJOR_WORKS_TO_BE_PALLNED
, INTERIOR_CONDITION_BRAND_NEW
, INTERIOR_CONDITION_GOOD_CONDITION
, INTERIOR_CONDITION_TO_BE_RENOVATED
GENERAL_CONDITION_UNKNOWN
, GENERAL_CONDITION_TO_BE_RENOVATED
, GENERAL_CONDITION_BRAND_NEW
, GENERAL_CONDITION_RENOVATED
, GENERAL_CONDITION_TO_BE_REFRESHED
, GENERAL_CONDITION_GOOD
, GENERAL_CONDITION_EXCELLENT
, GENERAL_CONDITION_DECREPIT
, GENERAL_CONDITION_TO_BE_BUILT
PARKING_UNKNOWN
, PARKING_GARAGE
, PARKING_PARKING
LAND_UNKNOWN
, LAND_BUILDING_PLOT
, LAND_AGRICULTURAL
, LAND_VINEYARD
, LAND_INDUSTRIAL
, LAND_POND
, LAND_FOREST
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
SELLER_TYPE_UNKNOWN
, SELLER_TYPE_AGENCY
, SELLER_TYPE_NETWORK
ALERT_MATCH_UNKNOWN
, ALERT_MATCH_PRICE
, ALERT_MATCH_CREATED
, ALERT_MATCH_OFFLINE
, ALERT_MATCH_MERGED
Response
The Status
type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by gRPC. Each Status
message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the API Design Guide.
The status code, which should be an enum value of [google.rpc.Code][google.rpc.Code].
A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the [google.rpc.Status.details][google.rpc.Status.details] field, or localized by the client.
A list of messages that carry the error details. There is a common set of message types for APIs to use.
A URL/resource name that uniquely identifies the type of the serialized protocol buffer message. This string must contain at least one "/" character. The last segment of the URL's path must represent the fully qualified name of the type (as in path/google.protobuf.Duration
). The name should be in a canonical form (e.g., leading "." is not accepted). In practice, teams usually precompile into the binary all types that they expect it to use in the context of Any. However, for URLs which use the scheme http
, https
, or no scheme, one can optionally set up a type server that maps type URLs to message definitions as follows: README.md _snippets api-ai-reference api-analytics-reference api-elasticimmo-reference api-geography-reference api-maps-reference api-search-alert-reference authentification.mdx doc favicon.png gen_swagger_analytics.sh gen_swagger_api_v2.sh gen_swagger_city.sh gen_swagger_dvf.sh gen_swagger_elasticimmo.sh gen_swagger_geography.sh gen_swagger_maps.sh images introduction.mdx mint.json swagger-analytics.json swagger-api-v2.json swagger-city.json swagger-dvf.json swagger-elasticimmo.json swagger-geography.json swagger-maps.json tmp.txt If no scheme is provided, https
is assumed. README.md _snippets api-ai-reference api-analytics-reference api-elasticimmo-reference api-geography-reference api-maps-reference api-search-alert-reference authentification.mdx doc favicon.png gen_swagger_analytics.sh gen_swagger_api_v2.sh gen_swagger_city.sh gen_swagger_dvf.sh gen_swagger_elasticimmo.sh gen_swagger_geography.sh gen_swagger_maps.sh images introduction.mdx mint.json swagger-analytics.json swagger-api-v2.json swagger-city.json swagger-dvf.json swagger-elasticimmo.json swagger-geography.json swagger-maps.json tmp.txt An HTTP GET on the URL must yield a [google.protobuf.Type][] value in binary format, or produce an error. README.md _snippets api-ai-reference api-analytics-reference api-elasticimmo-reference api-geography-reference api-maps-reference api-search-alert-reference authentification.mdx doc favicon.png gen_swagger_analytics.sh gen_swagger_api_v2.sh gen_swagger_city.sh gen_swagger_dvf.sh gen_swagger_elasticimmo.sh gen_swagger_geography.sh gen_swagger_maps.sh images introduction.mdx mint.json swagger-analytics.json swagger-api-v2.json swagger-city.json swagger-dvf.json swagger-elasticimmo.json swagger-geography.json swagger-maps.json tmp.txt Applications are allowed to cache lookup results based on the URL, or have them precompiled into a binary to avoid any lookup. Therefore, binary compatibility needs to be preserved on changes to types. (Use versioned type names to manage breaking changes.) Note: this functionality is not currently available in the official protobuf release, and it is not used for type URLs beginning with type.googleapis.com. Schemes other than http
, https
(or the empty scheme) might be used with implementation specific semantics.
Was this page helpful?