Skip to main content

​
Tango Update Store Contacts API

Generated from Tango Update Store Contacts API Integration Design Specification V0.5.docx in SharePoint folder 01 Common Integrations. OAS spec: store-contacts-inbound.yaml

​
Overview

Async REST API: client inserts/updates contacts attached to a store in Tango. The store must already exist; this API doesn’t create stores. Owner: Tango Analytics Spec version: 0.5 Status: Draft (auto-generated — needs review)

​
Base URLs

​
Authentication

Headers x-client + x-api-key.

​
Endpoints

​
Integration logic

  • The store referenced by store_number must already exist in Tango; contact loads against missing stores fail.
  • Upsert key: (store_number, role). The same role cannot exist twice on the same store.
  • Matching (store_number, role) → existing contact is updated.
  • Non-matching → new contact is created.

​
Data model (required ✅)

​
Validations

​
Open Questions / Assumptions

  • Host URL is placeholder <<hostname>>/<<context>> in source. Replaced with the standard Tango hosts as placeholders; confirm with the API team.
  • status allowed values: source mentions A and R. Assumed A = Active and R = Removed; confirm.
  • No exception handling / Fall Back scenarios — both sections are <TBD>.
  • Lookup codes for CONTACTS_ROLE are <TBD> in Appendix.

​
Changelog