Skip to main content

​
Tango Space Property Outbound API

Generated from Tango Space Property Outbound API Integration Design Specification V1.0.docx in SharePoint folder 03 Space Integrations. OAS spec: property-outbound.yaml

​
Overview

Async delta REST API: client retrieves Property records updated in Tango since the last integration run. Two-call pattern with gu_id and pagination (5000/page). Owner: Tango Analytics Spec version: 1.0 Status: Draft (auto-generated — needs review)

​
Endpoints

​
Integration logic

  • Delta API; updates to property_id do NOT trigger export.
  • Null fields are omitted from response.

​
Data model

​
Open Questions / Assumptions

  • longtitude typo — source mapping consistently uses longtitude (not longitude). Sample JSON also has longitude. Wire format unclear — confirm.
  • Field casing inconsistencies: address (lowercase) vs Address2 (PascalCase), Residual_sf (capital R) vs usable_sf (lowercase u), Owned/Subleased (PascalCase) vs everything else (lowercase). Preserved verbatim.
  • Owned/Subleased typed NUMBER but sample shows "0" (string). Treated as Y/N indicator. Confirm.
  • Test URL uses uspstestapi subdomain (USPS-specific?) — likely a client-specific staging environment. Confirm whether the standard testapi.tangoanalytics.com should be used.
  • Integration Logic has duplicate sentence (“This is a delta API which means any comments created…”). Looks copy-pasted from the MAC Comment Outbound spec. Source doc bug.

​
Changelog (compressed)