> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tangoanalytics.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Asset details inbound

# 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`](./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

| Environment | URL |
| - | - |
| Production | TBD (placeholder: `https://api.tangoanalytics.com`) |
| Test (SIT/UAT) | TBD (placeholder: `https://testapi.tangoanalytics.com`) |

## Authentication

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

## Endpoints

| Method | Path | Summary |
| - | - | - |
| PUT | `<TBD>` (placeholder: `/v1/assetmgmt/batch/assets`) | Submit asset records (async). |
| GET | `/v1/batch/status?gu_id=...` | Poll processing status. |

## Data model (required ✅)

| Field | Type | Req | Notes |
| - | - | - | - |
| `asset_id` | NUMBER | ✅ | Tango asset ID |
| `asset_instance_id` | NUMBER | ✅ | Tango asset instance ID |
| `asset_instance_number` | VARCHAR | ✅ | |
| `asset_master_number` | VARCHAR | ✅ | |
| `asset_instance_name` | VARCHAR | – | |
| `description` | VARCHAR | – | |
| `entity_number` | VARCHAR | – | Building/Location number |
| `asset_class` | VARCHAR | – | Lookup |
| `serial_number` / `tag_number` / `manufacturer` / `model_no` | VARCHAR | – | |
| `date_in_service` / `warranty_exp_date` / `date_of_purchase` / `warranty_start_date` | DATE `MM/DD/YYYY` | – | |
| `purchase_value` / `net_book_value` / `monthly_lease_payment` | NUMBER | – | |
| `vendor` | VARCHAR | – | Vendor number — must exist in Tango |
| `lease_begin_date` / `lease_end_date` | DATE | – | |
| `leasing_company` ⚠ | DATE → VARCHAR | – | Source types as DATE but content is text; see Open Questions |
| `status` / `asset_type` / `asset_owner` / `associated_entity_type` / `used_by_entity_type` / ` asset_condition` ⚠ | VARCHAR | – | All lookups |
| `model_name` | VARCHAR | – | |
| `useful_life` / `depreciation` / `warranty_period` | NUMBER | – | |
| `associated_entity_number` | VARCHAR | – | Value depends on type (Location/Building/Floor/Space/Person number) |
| `used_by_entity_number` | VARCHAR | – | Person number; must exist in Tango |
| `replacement_cost` | VARCHAR | – | Sample is `"150000"` (string in source despite numeric meaning) |
| `is_reservable` | VARCHAR | – | Lookup Y/N |
| `c_ext_attr1..27` | VARCHAR | – | Custom string attributes |
| `c_ext_lov1..5` | VARCHAR | – | Custom lookups |
| `n_ext_attr1..10` | NUMBER | – | Custom number attributes |
| `d_ext_attr1..5` | DATE | – | Custom date attributes |

## 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

| Ver | Date | Description | Author |
| - | - | - | - |
| 0.1 | 05/11/2023 | Initial Draft | Alpna Bansal |
| 0.2 | 04/02/2024 | Updated sample JSON and Data Mapping | Rahma Ouedraogo |
| 0.3 | 09/25/2024 | Updated Data Mapping | Ndry Kouakou |
| 0.4 | 04/23/2026 | Updated API architecture diagram | Alpna Bansal |