Table of Contents
Fields
Buildings have the same fields as schools.
| Field | Name | Description | Type | Required | 
|---|---|---|---|---|
 id  |  Building Id |   The internal Schoology ID that identifies the building. This field cannot be used in create operations; only update and read operations.  |   string  |  |
 title  |  Building Title |   The name of the building  |   string  |  yes | 
 address1  |  Street address line 1 |   The first line of the building’s street address  |   string  |  |
 address2  |  Street address line 2 |   The second line of the building’s street address  |   string  |  |
 city  |  City |   The city where the building is located  |   string  |  |
 state  |  State |   The state/province where the building is located  |   string  |  |
 postal_code  |  Postal code |   The postal code where the building is located  |   string  |  |
 country  |  Country |   The country where the building is located  |   string  |  |
 website  |  Website |   The building’s website address  |   string  |  |
 phone  |  Phone number |   The building’s phone number  |   string  |  |
 fax  |  Fax number |   The building’s fax number  |   string  |  |
 building_code  |  Building Code |   The configurable external ID of this building (used for imports and synchronization)  |   string  |  |
 picture_url  |  Profile Picture URL |   The full URL of the school’s profile picture  |   string  |  
Operations
view
View the buildings for a school
| Path |       |  
| Content |    none  |  
| Return |   An list of buildings containing building fields JSONXML  |  
Note
For other operations related to buildings (i.e. GET,POST,PUT,DELETE) you can treat buildings like schools and use the available school object endpoints. For example, to make a change to an existing building, you would use PUT /school/[building_id]. For more details, check out the School Object.