Skip to main content

​
Tango Spaces Outbound API

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

​
Overview

Async delta REST API: client retrieves Space 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

Auth: x-client + x-api-key.

​
Integration logic

  • Delta API.
  • Updates to space_id, building_id, floor_id, property_id, property_number, or property_description do NOT trigger export.
  • Null fields omitted from response.

​
Data model (selected)

​
Open Questions / Assumptions

  • c_ext_lov1..9 JSON keys have whitespace in source sample (" c_ext_lov1 "). c_ext_lov10 is clean. Almost certainly a doc-typo — wire format likely uses unspaced keys. Confirm.
  • Sample inconsistency for numeric extension attrs: n_ext_attr1 and n_ext_attr2 shown as 0 (number), but n_ext_attr3..10 shown as "" (empty string). Schema uses NUMBER throughout.
  • Status endpoint shown as ASYNCH=No in source while initial GET is ASYNCH=Yes. Inconsistent; assumed copy-paste error since the gu_id flow is async.
  • No required-field column in source.

​
Changelog (compressed)