Skip to main content
POST
CREATE Building

Authorizations

X-API-Key
string
header
required

Prophia API key — either an account key (grants admin level permissions) or a user key with the REST scope. Send it in the X-API-Key header, or equivalently as Authorization: Bearer <api-key>. JWTs are rejected on /rest endpoints with 401.

Path Parameters

accountId
string
required

Body

application/json

Fields for creating a Building under an existing Property. The address is geocoded on create, which is where the Building's lat and lng come from.

propertyId
string
required

Prophia UUID of Property the building belongs to. This Property must also belong to the api Account. Does not support passing Property.customId for this field.

Minimum string length: 1
buildingName
string
required

Display name for the building.

Minimum string length: 1
address
object
required

Street address of a Building. Prophia geocodes it on create and again whenever it changes, which is where the Building's lat and lng come from. state and zipcode are required for US and CA addresses and optional everywhere else.

customId
string

Your external identifier, for cross-referencing with your own systems.

buildingType
enum<string>

The asset type for the Building. Must be one of the listed values. Prophia treats it as a reference label only — it is not checked against the asset and does not affect data onboarding. Defaults to OFFICE when omitted.

Available options:
OFFICE,
INDUSTRIAL,
RETAIL,
MIXED_USE,
OTHER,
LIFE_SCIENCES,
MEDICAL_OFFICE,
FLEX
buildingClass
string

Market classification of the building (e.g. A, B, C). This is a subjective, referential value only and has no bearing on how this Building is treated in Prophia's system.

metroArea
string

Metro market the building belongs to. This is a subjective, referential value only and has no bearing on how this Building is treated in Prophia's system.

Response

OK

Representation of a building. All Buildings have one Property association. Multiple Buildings can be associated with the same Property to represent a campus or other multi-building asset.

id
string
read-only

Prophia internal Building ID (UUID)

propertyId
string
read-only

Pointer to the Property this Building is associated with.

buildingName
string

Display name of the building. Must be unique within the same Property. Can be duplicated with other Buildings in the Account (i.e. Two Properties in the Account can have a Building called 'Building 1').

address
object

Street address of the building.

onboardingStatus
enum<string>
read-only

How far this building has progressed through Prophia's onboarding process. Leases, BuildingSpaces, and Tags are considered incomplete until onboarding completes for the Building.

Available options:
NOT_STARTED,
INITIAL_SETUP,
ONBOARDING_IN_PROGRESS,
ONBOARDING_COMPLETE
activeStatus
enum<string>
read-only

Operational state of the building record. An ACTIVE status indicates that the building has been fully onboarded and handed off by the Prophia team. An INACTIVE status indicates a Building that will no longer receive updates to its data and is essentially a purely historical representation of the asset. Other statuses show the Building moving through the systems automated processing states and review points.

Available options:
ACTIVE,
INACTIVE,
WORK_IN_PROGRESS,
QA_PENDING,
AI_PROCESSED
customId
string

Your external identifier for the building, for cross-referencing with your own systems. Prophia does not rely on this value in any way.

implementationManager
string
read-only

Prophia implementation manager responsible for onboarding and reviewing the data in this Building. This is not the account manager.

buildingType
enum<string>

The Asset type for the Building. This is a subjective reference value only, is not validated, and does not affect data onboarding.

Available options:
OFFICE,
INDUSTRIAL,
RETAIL,
MIXED_USE,
OTHER,
LIFE_SCIENCES,
MEDICAL_OFFICE,
FLEX
buildingClass
string

Market classification of the building (e.g. A, B, C). This is a subjective reference value only, is not validated, and does not affect data onboarding.

metroArea
string

Metro market the building belongs to (e.g. Seattle Metropolitan Area. This is a subjective reference value only, is not validated, and does not affect data onboarding.

lat
number
read-only

Latitude in decimal degrees. Derived automatically from the address when the building is created and re-geocoded whenever the address is changed; coordinates cannot be supplied directly. A geocode that fails or returns no match leaves the previously stored coordinates in place, so lat/lng may reflect an earlier address; a building whose address has never geocoded successfully has no coordinates at all.

lng
number
read-only

Longitude in decimal degrees. Derived alongside lat from the same geocode, and subject to the same staleness caveat.

propertyType
enum<string>
read-only

Whether the parent property holds a single building or multiple.

Available options:
MULTI_BUILDING,
SINGLE_BUILDING
totalRentableSquareFootage
integer<int32>
read-only

Cached total rentable square footage from the last stacking-plan build; may lag current values while leases are in onboarding. Use the stacking plan for point-in-time occupancy.

squareFootageLeased
integer<int32>
read-only

Cached leased square footage from the last stacking-plan build; may lag current values while leases are in onboarding. For a Building Space to count towards leased square footage it must have either an active/commenced lease or a lease with a future commencement date referencing that space. Use the stacking plan for point-in-time occupancy.

squareFootageOccupied
integer<int32>
read-only

Cached occupied square footage from the last stacking-plan build; may lag current values while leases are in onboarding. For a Building Space to count towards occupied square footage it must have an active/commenced lease referencing that space.Use the stacking plan for point-in-time occupancy.

squareFootageVacant
integer<int32>
read-only

Cached vacant square footage from the last stacking-plan build; may lag current values while leases are in onboarding. For a Building Space to count towards vacant square footage, it can't have any active/commenced lease referencing that space.Use the stacking plan for point-in-time occupancy.

leases
object[]

Leases in this building; only populated when include=leases is present as a request parameter.

documents
object[]
read-only

Building-level documents (rent rolls, stacking plans); only populated when include=documents is present as a request parameter.

spaces
object[]
read-only

Spaces in this building, archived and non-archived alike; only populated when include=spaces is present as a request parameter.

customFields
object[]
read-only

The Building's values for its active Building Custom Fields as name/value pairs, sorted by field name; only populated when include=customFields is present as a request parameter. Manage the fields and assignments themselves through the Custom Fields endpoints.