​

Tango User Roles Reconcile API (non-BU)

Generated from Tango nonBU User Roles Reconcile API Integration Design Specification V0.7.docx in SharePoint folder 01 Common Integrations. OAS spec: user-roles-reconcile-nonbu.yaml

​

Overview

​

Differences from the BU variant

​

Base URLs

​

Authentication

​

Endpoints

​

Filter parameters (mutually exclusive)

​

Integration logic

​

Data model

{
  "user_name": "test.user@abc.com",
  "first_name": "test",
  "last_name": "user",
  "email": "test.user10.04.22@abc.com",
  "user_type": "CORPORATE",
  "sso": "Y",
  "status": "A",
  "default_country": "USA",
  "data_access_level": "F",
  "brands": "Tango Standard",
  "countries": [
    {
      "country": "USA",
      "regions": "ALL",
      "roles": " ",
      "entity_security": [
        { "entity_type": "TARGET", "full_access": "Y", "restrictions": [] },
        { "entity_type": "SITE",   "full_access": "Y", "restrictions": [] },
        { "entity_type": "STORE",  "full_access": "Y", "restrictions": [] },
        { "entity_type": "PROJECT","full_access": "Y", "restrictions": [] },
        { "entity_type": "LEASE",  "full_access": "Y", "restrictions": [] }
      ]
    }
  ]
}

​

Open Questions / Assumptions

• brands field is a flat string ("Tango Standard") per the source sample. The BU variant has it as a nested-object array. Asymmetric shapes between BU and non-BU variants — confirm intended.
• roles field sample value is " " (single space). Likely empty access on this sample; confirm whether real records carry role lookup codes here.
• entity_type values include TARGET, SITE, STORE, PROJECT, LEASE — the BU variant lists TARGET, SITE, LEASE etc. Confirm the complete enum.
• No audit fields (creation_date / last_login_date etc.) in the non-BU response — the BU variant added these in v0.6. Confirm whether they should be present here too.

​

Changelog