Skip to main content

​
Tango Asset Details Inbound API

Generated from Tango Asset Details Inbound API Integration Design Specification V0.4.docx in SharePoint folder 01 Common Integrations. OAS spec: asset-details-inbound.yaml

​
Overview

Async REST API for posting asset detail records from a client system into Tango. Client PUTs a batch of asset records; Tango returns a gu_id and the client polls /v1/batch/status for processing outcomes. Owner: Tango Analytics Spec version: 0.4 Status: Draft (auto-generated — needs review)

​
Base URLs

​
Authentication

Headers x-client + x-api-key, required on every call.

​
Endpoints

​
Data model (required ✅)

​
Open Questions / Assumptions

  • Source/Destination header inconsistency — doc lists Source: tango / Destination: client system but the description is “post details … to Tango”. Spec treats this as inbound (Client → Tango) per the description. Confirm.
  • URL is <TBD> — placeholder used (/v1/assetmgmt/batch/assets). Confirm with API team.
  • Field name with leading space: source JSON has " asset_condition" (note the leading space). Preserved verbatim. If the wire format does NOT have the space, this should be corrected.
  • leasing_company typed DATE in data-mapping table but sample data and field name suggest a string. Schema uses string.
  • replacement_cost typed VARCHAR in mapping but contains numeric values. Preserved as string.
  • No validations are documented in the source (section 4.5 is empty). No error conditions listed beyond Invalid Asset ID (TBD).
  • Exception handling / Fall Back scenarios are <TBD> in the source.

​
Changelog