When using BDP Command to send emails you can include almost any data contained in BDP in the email template. The same is true for Word document templates. Developers will also want to make use of this data which is all available via the API. There are additional items available, however because they are not commonly used they have been excluded from this list. Please contact us if you don’t see an item you require. What follows is a complete listing of all system “hooks” for properties.
| [descText] |
Full description |
| [epcBand] |
EPC band letter |
| [cTaxBand] |
Council tax band letter |
| [gardenType] |
Garden type, eg. Front, surrounding, etc. |
| [parkingType] |
Parking type, eg. Garage, off-street, etc. |
| [tenureType] |
Tenure, eg. Freehold, leasehold |
| [summaryText] |
Property summary from Property Details widget |
| [viewingDetails] |
Viewing details, eg. By appointment with agent, etc. |
| [espcSlogan] |
ESPC slogan |
| [genNotes] |
Contents of the Notepad widget. NOTE: Do not send outside your organisation! |
| [localRef] |
Firm’s internal property reference |
| [viewingMInfoviewingMInfo] |
Viewing Management info from the management widget |
| [keyMInfo] |
Key management info from the Management widget |
| [signMInfo] |
Sign management info from the Management widget |
| [surveyorName] |
Surveyor name |
| [surveyorInstructions] |
Surveyor instructions |
| [espcId] |
ESPC ID (integer). Can be used to build a URL to link to the property on ESPC |
| [escpHrId] |
ESPC Home Report ID (integer). Can be used to build a link to the ESPC home report. |
| [shMovieLink] |
Full URL to Shoot Home video |
| [addrL3] |
Address line 3 |
| [paperAddress] |
Address displayed in the ESPC newspaper. |
| [branch_id] |
Branch ID (integer). Could be used as part of a URL to display properties from a particular branch. |
| [property_id] |
BDP property ID (integer). Can be used as part of a URL to link to the property. |
| [houseNo] |
Number or name of property |
| [streetName] |
Street or road name |
| [pName] |
Property name |
| [addrL1] |
Address line 2 (line after the street name) |
| [addrL2] |
Address line 3 |
| [town] |
Town or city |
| [postcode] |
postcode |
| [formatAddress] |
Concatenated “display” address comprising all separate address fields. |
| [dispAddress] |
The Display address if this has been entered into the separate display address field |
| [lat] |
GPS Latitude of property |
| [lng] |
GPS longditude of the property |
| [mapData] |
Map data – call for details |
| [askingPrice] |
Asking price (integer). Unformatted. |
| [sqmHouse] |
Floor area of the house in square metres |
| [sqmLand] |
Land area in square metres |
| [bedRooms] |
Number of bedrooms (integer) |
| [livingRooms] |
Number of living rooms (integer) |
| [bathRooms] |
Number of bathrooms (integer) |
| [garden] |
Type of garden |
| [noShowerRooms] |
Number of shower rooms (integer) |
| [noKitchens] |
Number of kitchens (integer) |
| [noToilets] |
Number of toilets (integer) |
| [espcDistrict] |
ESPC district and ESPC Area |
| [espcDistrictName] |
ESPC district |
| [espcAreaName] |
ESPC Area |
| [pLive] |
Property live (integer)? 1=yes, 0=no |
| [typeNames] |
Property type name (array so can be more than one). Example usage {{ propertyDetails.typeNames.0 }} |
| [letFrequency] |
Let frequency (Lettings only) |
| [detailPath] |
Full URL to property on firm’s website if using the jQuery method. NOTE: Will not work if using the API |
| [sellingStatus] |
Selling status, e.g. Available |
| [statusClass] |
CSS class for selling status can be used to style different selling statuses |
| [currencySymbol] |
Currency symbol, e.g. £ |
| [onlineStateLabel] |
Online state, e.g. Online |
| [estimatedValue] |
Estimated value as an integer (no currency symbol or formatting) |
| [hrValue] |
Home Report value as an integer (no currency symbol or formatting) |
| [hrValueFormat] |
Home report value, formatted including currency symbol |
| [priceType] |
Price type, e.g. Fixed, Offer over, etc. |
| [priceTypeLabel] |
Price type label, e.g. Fixed Price |
| [outputSoldPriceCMS] |
Sold price, fully formatted including currency symbol. |
| [outputAskingPrice] |
Fully formatted asking price with currency symbol and thousands separator |
| [floatAskingPrice] |
Unformatted asking price (integer) |
| [outputHrValue] |
Fully formatted home report value with currency symbol and thousands separator => £425,000 |
| [dateCreated] |
Date listing created in UNIX time format (see http://i.bdphq.com/email-date-placeholder-formats/). |
| [marketDateFormat] |
Date property came on market, formatted, e.g. 15 Nov 2013. |
| [marketingDateFormat] |
Date and time property came on market, formatted, e.g. 15 Nov 2013 13:00. |
| [marketDate] |
Market date in Unix time format (see http://i.bdphq.com/email-date-placeholder-formats/). |
| [dateListed] |
Property listing date in Unix time format (see http://i.bdphq.com/email-date-placeholder-formats/). |
| [closingDateFormat] |
Closing date, formatted, e.g.15 Nov 2025 13:00. |
| [closingDate] |
Closing date in Unix time format (see http://i.bdphq.com/email-date-placeholder-formats/). |
| [entryDateFormat] |
Entry date formatted. e.g.16 Jan 2025. |
| [entryDate] |
Entry date created in UNIX time format (see http://i.bdphq.com/email-date-placeholder-formats/). |
| [soldDateFormat] |
Sold date, formatted, e.g. 15 Nov 2025. |
| [soldDate] |
Sold date in UNIX time format (see http://i.bdphq.com/email-date-placeholder-formats/). |
| [dateOfferAcceptedFormat] |
Date offer accepted, formatted, e.g. 15 Nov 2025. |
| [dateOfferAccepted] |
Date offer accepted in UNIX time format (see http://i.bdphq.com/email-date-placeholder-formats/). |
| [dateMissivesConcludedFormat] |
Date missives concluded, formatted, e.g. 15 Nov 2025. |
| [dateMissivesConcluded] |
Date missives concluded in UNIX time format (see http://i.bdphq.com/email-date-placeholder-formats/). |
| [hrPDate] |
Home report published date, formatted date2024-07-03 11:41:26. |
| [gasSafetyFormat] |
Gas safety certificate due date, formatted. |
| [purchaseDate] |
Date seller purchase the property. Freetext data field. |
| |
| A UNIX timestamp is a simple integer that repesents the number of seconds from 1st January 1970. |
| Use the stats array: |
{{ propertyDetails.stats.placeHolder }} |
| [notesInterest] |
Number of notes of interest (integer) |
| [offersLogged] |
Number of offers logged (integer) |
| [closingDate] |
=> |
| [gasSafety] |
=> |
| [workOrders] |
Number of work orders (integer) |
| [noViewings] |
Number of viewings (integer) |
| [dRequestsOffice] |
Number of details requests via the office (integer) |
| [dRequestsWebsite] |
Number of details requests via your website (integer, only available if using the jQuery snippet) |
| [dRequestsRM] |
Number of details requests via Rightmove (integer) |
| [dRequestsZoopla] |
Number of details requests via Zoopla (integer) |
| [dRequestsS1] |
Number of details requests via S1 (integer) |
| [dRequestsESPC] |
Number of details requests via ESPC (integer) |
| [hrRequestsESPC] |
Number of home report requests via ESPC (integer) |
| [hrRequestsOffice] |
Number of home report requests via the ofice (integer) |
| [setOnline] |
Date property set online in Unix time format |
Use: {{ propertyDetails.rooms.0.placeholder }}
Supporting HTML in email preambles