API INSTALLATION EXPLAINER
Your website, always current
www.sub800.com
WHAT IT IS
Imagine your website always showing the latest available space, without you lifting a finger. One simple piece of code, and every building we add, update or remove appears on your site automatically. Fresh listings, zero admin — and the enquiries come to you.
HOW IT WORKS
Live, and self-updating A one-time set-up, then it looks after itself — here's the flow.
We keep it current
The feed syncs
Your site shows it
New buildings, price changes and lets — our availability is kept live by sub800.
Our integration pushes every change to your website automatically, in the background.
Always-current listings appear on your site, styled as your own.
Set up once, current forever Your web person adds the code once. From then on, your listings stay in step with our live availability with no manual updating, ever.
Live Availability Integration
4
THE BENEFITS
Why Partners Add It A better website for your clients, and less work for you.
Always current
Zero admin
Every space we add, update or remove changes on your site automatically — nothing goes stale.
No manual updating, ever. It maintains itself in the background.
More to show
Enquiries to you
Dozens of live, curated listings on your site instantly — more for clients to browse.
Clients browse on your site and enquire through you — you stay the trusted contact.
On brand
Quick to add
Styled to match your website and presented as your listings, not a third party's.
A single snippet — your web person can have it live in minutes.
Live Availability Integration
5
GET IT INSTALLED
Installation Instructions Endpoint Details HTTP method
GET
Endpoint
https://sub800.com/api/all-properties-v2
Authentication
No authentication was required in the checked example. If access rules change, follow the API owner's current
Request body
None
Query parameters
None required for the example request
Test the API in Postman 1. Open Postman and create a new HTTP request. 2. Choose GET as the method. 3. Paste https://sub800.com/api/all-properties-v2 into the URL field. 4. Open the Headers tab. No special headers are required for the example; optionally set Accept to application/json. 5. Do not add a request body or query parameters for this endpoint. 6. Click Send. 7. Confirm the response status is successful and the Body tab displays JSON. Use Pretty view to expand the properties array. Equivalent cURL request: curl --request GET "https://sub800.com/api/all-properties-v2" --header "Accept: application/json"
Response Structure 1. The root response contains a properties array. Each array item contains three main sections: 2. property — details for one property listing. 3. galleries — an array of gallery images associated with that property. 4. Amenities — an array of amenities, each with an ID, image URL, title, and description. 5. Simplified structure:
Live Availability Integration
6
GET IT INSTALLED
{ "properties": [ { "property": { "...property fields..." }, "galleries": [ { "id": 19212, "property_id": 4685, "image_url": "https://sub800.com/public/assets/property_img/4685/6734815bd1b76.jpg" } ], "Amenities": [ { "id": 17, "image": "https://sub800.com/public/assets/property_includes_img/692723df8eba6.png", "title": "Access Control", "description": "Allows you to gain access to your space a card system over a traditional lock and key" } ] } ] }
4. Property field reference Field
Type
Meaning / notes
id
Integer
Unique property identifier. Example: 4685.
title
String
Property/listing title.
slug
String
URL-friendly listing identifier.
short_description
String or null
Short listing summary; may be null.
description
String or null
Long-form property description.
location
String or null
Property address/location as stored for the listing.
price
Number or null
Existing price field retained in the response.
propertyarea_sqft
Number or null (intended)
Property area in square feet. Example: 1243. It should be consumed as a
floor
String or null
Floor label, e.g. 1st.
featuredimage
URL string or null
Featured image URL.
Live Availability Integration
7
GET IT INSTALLED
latitude
Number (intended)
Latitude from the property's initialPosition value. The supplied
longitude
Number (intended)
Longitude from the property's initialPosition value. The supplied
postcode
String or null
Postal/ZIP code. Keep as a string.
city
String or null
City name.
country_code
String
Country code, e.g. GB.
currency
String
Currency code, e.g. GBP.
is_occupied
String or null
Occupancy value, e.g. no. Treat according to the API's defined values.
workspace_address
String or null
Workspace address; mapped from the property location.
pcm
Number or null
Price per calendar month; mapped from the property's price.
gbp
String
Currency label in the supplied response, e.g. GBP.
all_inclusive
String
Pricing label in the supplied response: all_inclusive.
minimum_desks
Integer or null
Minimum desk count; mapped from desk. Example: 18 or may be null.
maximum_desks
Integer or null
Maximum desk count; mapped from maxdesk. Example: 28 or may be null.
minimum_term
Integer or null
Minimum term value from termOfOccupancy, converted to an
Gallery Images The galleries array contains all gallery images returned for that property. Each gallery item includes: id — gallery record ID. property_id — ID of the associated property. image_url — full URL of the image. Example image URL pattern: https://sub800.com/public/assets/property_img/{property_id}/{image_filename} Use each image_url directly to display or open the image. A property may have zero, one, or many gallery images.
Amenities Amenities is an array (capital A in the current response). Each item contains: id — amenity identifier. image — full URL of the amenity icon/image. title — amenity name, e.g. Access Control or Air Conditioning. description — explanatory text for the amenity. Example image URL pattern: https://sub800.com/public/assets/property_includes_img/{image_filename}
Live Availability Integration
8
GET IT INSTALLED
latitude
Number (intended)
Latitude from the property's initialPosition value. The supplied
longitude
Number (intended)
Longitude from the property's initialPosition value. The supplied
postcode
String or null
Postal/ZIP code. Keep as a string.
city
String or null
City name.
country_code
String
Country code, e.g. GB.
currency
String
Currency code, e.g. GBP.
is_occupied
String or null
Occupancy value, e.g. no. Treat according to the API's defined values.
workspace_address
String or null
Workspace address; mapped from the property location.
pcm
Number or null
Price per calendar month; mapped from the property's price.
gbp
String
Currency label in the supplied response, e.g. GBP.
all_inclusive
String
Pricing label in the supplied response: all_inclusive.
minimum_desks
Integer or null
Minimum desk count; mapped from desk. Example: 18 or may be null.
maximum_desks
Integer or null
Maximum desk count; mapped from maxdesk. Example: 28 or may be null.
minimum_term
Integer or null
Minimum term value from termOfOccupancy, converted to an
Gallery Images The galleries array contains all gallery images returned for that property. Each gallery item includes: id — gallery record ID. property_id — ID of the associated property. image_url — full URL of the image. Example image URL pattern: https://sub800.com/public/assets/property_img/{property_id}/{image_filename} Use each image_url directly to display or open the image. A property may have zero, one, or many gallery images.
Amenities Amenities is an array (capital A in the current response). Each item contains: id — amenity identifier. image — full URL of the amenity icon/image. title — amenity name, e.g. Access Control or Air Conditioning. description — explanatory text for the amenity. Example image URL pattern: https://sub800.com/public/assets/property_includes_img/{image_filename}
Live Availability Integration
9
GET IT INSTALLED
Data type notes for client integration In the supplied sample, propertyarea_sqft, latitude, and longitude are shown as quoted strings. If the client expects numeric JSON values, the API response should be adjusted to return them without quotes, for example: { "propertyarea_sqft": 1243, "latitude": 51.5126085, "longitude": -0.0727 } Until the API output is updated, clients should parse these three fields carefully and convert them to numbers in their application where appropriate. Do not convert postcode, IDs with leading zeros, URLs, descriptive text, currency codes, or label fields to numbers. maximum_desks may legitimately be null. A null value means no maximum value was supplied in that response; do not automatically replace it with zero.
Errors and troubleshooting Issue
What to check
Could not connect / timeout
Check internet access and confirm the endpoint URL is correct. Retry after a short interval.
404 Not Found
Check the URL path carefully: /api/all-properties-v2.
401/403 response
The request may be subject to updated access controls. Contact the API owner for current authentication/permission
Response is HTML instead of JSON
Check that the URL is the API endpoint and inspect the response status and headers.
Empty properties array
The endpoint may currently have no records matching its server-side filter. Confirm expected data with the API owner.
Image does not load
Open the full image URL directly and confirm the image remains available.
A field is null
Handle null values in the client rather than assuming every property has every optional field.
Important behavior and integration notes The response uses the exact key Amenities with a capital A. JSON keys are case-sensitive. The existing price and location fields are retained alongside pcm and workspace_address. The supplied mapping uses price for pcm, location for workspace_address, desk for minimum_desks, maxdesk for maximum_desks, and termOfOccupancy for minimum_term. The endpoint returns Public listings only. Public status does not guarantee that a property is available or unoccupied. The API returns a list, so client code should iterate over properties rather than assume only one listing. Use image URLs from the response instead of reconstructing filenames on the client.
Live Availability Integration
10
GET IT INSTALLED
Listing lifecycle: edits, Landing status, and deletion This section explains how listing changes should be understood by API consumers. The endpoint returns a snapshot of listings when requested; it does not push notifications or change events. When a listing is edited When property details are edited in SUB800, the changes are reflected immediately in the API data. Send a new GET request to retrieve the latest values. Use property.id to match the updated listing with a record stored in your application. When a listing is set to Landing (hidden from the API) The API returns Public listings only. A listing set to Landing or another non-Public status is excluded from the response. Send a new GET request to retrieve the current list. If a property is no longer returned, it is absent from the current API result. Since only Public listings are returned, a missing property may have been set to Landing or another non-Public status, or it may have been deleted. Do not assume absence alone means the property was deleted. When a listing is deleted Properties are soft-deleted. Once a property is deleted, it is removed from the API response immediately. Send a new GET request to retrieve the updated list. The API does not send a dedicated deletion event or notification. How quickly are changes reflected? Property edits and soft deletions are reflected immediately in the API data. Status changes that make a listing non-Public also affect whether it appears in the result. API consumers must send a new GET request to retrieve the latest response; the API does not automatically push updates or notifications. Recommended integration behaviour Use property.id as the stable identifier when refreshing records. Send a new GET request whenever your application needs the latest listing data. Handle properties missing from a response according to your synchronization policy; a missing property may be hidden because it is non-Public or may have been deleted. Do not assume webhooks, deletion notifications, or change events are available; this endpoint does not send them. Do not treat Public status as a guarantee that a property is available or unoccupied.
Quick Integration Checklist ☐ Send GET request to the endpoint. ☐ Check HTTP status and parse JSON. ☐ Read the properties array. ☐ Read property fields and handle null values. ☐ Loop through galleries and display image_url values. ☐ Loop through Amenities and display image, title, and description. ☐ Confirm numeric handling for propertyarea_sqft, latitude, and longitude. ☐ Use property.id to match records across refreshes. ☐ Agree how to handle listings that disappear from the response. ☐ Do not interpret status = 0 / Public as an availability guarantee.
Live Availability Integration
11
Let’s Talk If you need support with installing our live availability integration code, then do not hestiate to reach out to our team enquiries@sub800.com 07400 145 258 www.sub800.com