Skip to main content

​
Tango Space Area Outbound API

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

​
Overview

Async delta REST API: client retrieves Space Area 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 space_area_id, building_id, or floor_id do NOT trigger export.
  • Null fields omitted from response.

​
Data model

​
Open Questions / Assumptions

  • Type mismatches across building_number / floor_number / property_number — mapping says NUMBER but samples are strings (some with leading zeros / alphanumeric like REGION 2). Schema follows mapping; runtime may emit strings.
  • number_of_shifts / shift_length typed VARCHAR but samples are numeric (2, 8). Schema uses NUMBER.
  • status allowed values not enumerated — sample is blank.
  • Source version 0.9 dated 07/29/2205 — clearly a typo (2025). Cosmetic only.
  • available_occupancy sample 0.3 suggests fractional occupancy; confirm semantic.

​
Changelog (compressed)