Skip to main content

​
Tango Customer / Supplier Outbound API

Generated from Tango Customer-Supplier Outbound API Integration Design Specification V0.3.docx in SharePoint folder 01 Common Integrations. OAS spec: customer-supplier-outbound.yaml

​
Overview

Async delta REST API: client retrieves customer or supplier records from Tango (the supplier module produces both; record_type disambiguates). Two-call pattern with gu_id and pagination (5000/page). Owner: Tango Analytics Spec version: 0.3 Status: Draft (auto-generated — needs review)

​
Base URLs

​
Authentication

Headers x-client + x-api-key.

​
Endpoints

​
Integration logic

  • Delta API: only records updated after the last integration run are returned.
  • record_type distinguishes Customer vs Supplier.
  • insert_update_flag is I for new records or U for updates.
  • ein_ssn is an encrypted string — Tango shares the decryption key with the client out-of-band.
  • Null fields are omitted from response JSON.

​
Data model (no required-field column)

​
Open Questions / Assumptions

  • Direction inconsistency: header Source: CLIENT SYSTEM / Destination: TANGO contradicts the description (“exporting from Tango to the client”). Treated as outbound per the description.
  • Field name casing mismatch between mapping (Partner, Prequalified, City, State, Zip, Country, Status, Email, Fax, PascalCase) and the sample JSON (all lowercase). Mapping preserved verbatim — confirm wire format.
  • ein_ssn encryption: confirm encryption algorithm and key-exchange mechanism with Tango onboarding before production use.
  • country sample shows "null" (string null, not JSON null). May be a doc typo; treated as a regular string.

​
Changelog