Integrations
Read which of your buildings are connected to which integrations, how their latest syncs went, and how many documents each building holds in Findable — together with how you group it, through its affiliation and portfolios. One endpoint covers every integration, so connecting a building to a new source shows up as another entry rather than needing a new endpoint.
Building sync status
/v1/building_owners/{buildingOwnerId}/integration-statusOne entry per building the API key can read — connected to an integration or not — with its document count, its affiliation and portfolios, and, for each connected integration, the status of the most recent sync run and when a full sync last completed. Built for joining sync coverage into external dashboards such as Power BI, grouped the way you organise your estate. A key scoped to individual buildings receives only those buildings.
Authentication
x-api-key header
buildingOwnerIdstringrequiredBuilding owner / customer ID.
Examples
curl -H "x-api-key: YOUR_API_KEY" \
"https://api.findable.ai/v1/building_owners/cust-456/integration-status"200Sync status returned403Building owner access denied404Building owner not found500Unexpected server error
All endpoints may also return 429 (rate limit) and 500 (server error). See Common Patterns for details.
buildingsBuildingIntegrationStatus[]One entry per readable building, connected or not.buildings[].building_idstringFindable building ID.buildings[].building_namestringBuilding display name.buildings[].external_idstring | nullYour own identifier for the building (e.g. an FM-system or register code), as set on the building in Findable. The stable join key against external systems; null when none is set.buildings[].affiliationstring | nullThe building's Affiliation field in Findable — owner, location or any other grouping you maintain on the building itself. null when it is not set.buildings[].portfoliosBuildingPortfolio[]Portfolios the building belongs to, in no particular order. Empty when it belongs to none; a building can sit in several.buildings[].portfolios[].idstringFindable portfolio ID.buildings[].portfolios[].namestringPortfolio display name.buildings[].number_of_filesintegerDocuments on the building in Findable, from every source combined (integrations and manual uploads). A building-level total — it is not split per integration, so sum it per building, not per integration entry.buildings[].integrationsBuildingIntegration[]One entry per integration the building is connected to. Empty when the building has none.buildings[].integrations[].source'sharepoint' | 'interaxo' | 'plania' | 'famac' | 'dalux' | 'dalux_box' | 'google_drive'The integration. New sources may be added over time; treat unknown values as another integration rather than an error.buildings[].integrations[].sync_status'pending' | 'syncing' | 'synced' | 'error' | nullStatus of the most recent sync run from this source: 'pending' (SharePoint only: set up, first sync not started), 'syncing', 'synced', or 'error' (the run failed or was cancelled). It reflects the last recorded run — not a live health probe, and not a guarantee that every document has landed: a SharePoint site or drive that has since been removed keeps reporting its last recorded status (often 'synced') until a sync run records the error. null when no run has been recorded yet.buildings[].integrations[].last_synced_atstring | nullWhen a full sync from this source last completed (ISO 8601). Routine SharePoint webhook imports do not update it, so an older value does not mean syncing has stopped. For the other integrations it is read from the last 50 recorded runs, so it is null if none of those completed.buildings[].integrations[].export_folderstring | nullName of the folder Findable exports documents back to, for integrations that take write-back (SharePoint today). null when there is no configured export destination, and always null for import-only integrations.unavailable_sourcesstring[]Integrations whose state could not be read for this response, usually empty. For a source listed here, a missing entry or a null sync_status means 'unknown', not 'not connected' or 'never synced' — retry later.
Response
{
"buildings": [
{
"building_id": "bld-789",
"building_name": "Harbour House",
"external_id": "FM-0042",
"affiliation": "Kristiansund",
"portfolios": [
{ "id": "pf-123", "name": "Atlanten videregående skole" }
],
"number_of_files": 812,
"integrations": [
{
"source": "sharepoint",
"sync_status": "synced",
"last_synced_at": "2026-09-30T04:12:00.000Z",
"export_folder": "Harbour House – Findable"
},
{
"source": "interaxo",
"sync_status": "error",
"last_synced_at": "2026-09-28T02:00:00.000Z",
"export_folder": null
}
]
},
{
"building_id": "bld-790",
"building_name": "Quay Works",
"external_id": null,
"affiliation": null,
"portfolios": [],
"number_of_files": 0,
"integrations": []
}
],
"unavailable_sources": []
}