Skip to main content

​
Tango Asset Details Outbound API

Generated from Tango Asset Details Outbound API Integration Design Specification V1.0.docx in SharePoint folder 01 Common Integrations. OAS spec: asset-details-outbound.yaml

​
Overview

Async delta REST API: client retrieves asset detail records that were created/updated in Tango since the last integration run. Two-call pattern with gu_id; null fields are omitted from the response JSON. Owner: Tango Analytics Spec version: 1.0 Status: Draft (auto-generated — needs review)

​
Base URLs

​
Authentication

Headers x-client + x-api-key.

​
Endpoints

​
Integration logic

  • Delta semantics: only records updated after the last integration run are returned.
  • Same gu_id may be polled multiple times for the same record set.
  • Null/unconfigured fields are omitted from the response.

​
Data model

The source data-mapping table does NOT mark any field as required for the outbound direction. All fields are emitted only when populated in Tango.

​
Open Questions / Assumptions

  • Source typo purchage_value — almost certainly should be purchase_value. The inbound spec uses the correct spelling, creating an asymmetry. Confirm with API team.
  • Field case inconsistency between mapping table and sample JSON: Tag_number vs tag_number, Model_no vs model_no. Preserved per mapping; verify actual wire format.
  • Data type typo VARCAHR appears for property_number and building_number. Treated as VARCHAR.
  • leasing_company typed DATE but contents are strings (e.g., a company name). Schema uses string.
  • No required-field annotation for the outbound direction.

​
Changelog