​

Tango Vendor (Supplier Sites) Inbound API

Generated from Tango Vendor API Integration Design Specification V1.3.docx in SharePoint folder 01 Common Integrations. OAS spec: vendor-inbound-api.yaml

​

Overview

Async REST API: client PUTs vendor / supplier-site records to Tango. Creates / updates supplier sites with addressing, payment, and banking info. Owner: Tango Analytics Spec version: 1.3 Status: Draft (auto-generated — needs review)

​

Base URLs

​

Authentication

Headers x-client + x-api-key.

​

Endpoints

​

Integration logic

• Upsert key: (supplier_number, supplier_site_number).
• Supplier_type defaults to LEASE if blank.
• Status = A / I (Active / Inactive).

​

Data model (required ✅)

​

Validations (sample)

1. supplier_number null → supplier_number is missing or empty
2. status null → Status is missing or empty
3. status not in (A, I) → Status does not match expected value
4. Supplier_type not in (LEASE, PROJECT, ALL) → Supplier Type does not match expected value

​

Open Questions / Assumptions

• PascalCase / lowercase casing inconsistency for many fields in source data mapping (Supplier_type, Supplier_number, Country, Status, City, State, Zip, Email, Fax, Partner, Prequalified). Preserved verbatim — confirm actual wire format.
• Source label typo “Suppler Site Name” — preserved.
• record_key type inconsistency in error sample: one entry shows 0010 (no quotes — could be number) and another "0005-005" (string). Modelled as oneOf.
• Lookup codes are <TBD> in Appendix.

​

Changelog (compressed)