Skip to main content

​
Tango User Provisioning API (non-BU)

Generated from Tango User Provisioning API Integration Design Specification_non BU V1.2.docx in SharePoint folder 01 Common Integrations. OAS spec: user-provisioning-nonbu-api.yaml

​
Overview

Async REST API: same endpoint as the BU User Provisioning API (/v1/usermgmt/batch/users) but for client environments without a Business Unit layer. The brands[] items have no business_unit field — access scopes by Brand / Country / Region / Role only. Owner: Tango Analytics Spec version: 1.2 Status: Draft (auto-generated — needs review)

​
Differences from the BU variant

The integration logic, validations, GENERAL_USER special case, inactivation flow, and entity-security model are otherwise identical to the BU variant — see user-provisioning-bu-api.md for the full details.

​
Base URLs

​
Authentication

Headers x-client + x-api-key.

​
Endpoints

​
Data model — Brand Assignment (non-BU, required ✅)

​
Open Questions / Assumptions

  • Same endpoint for BU and non-BU: both specs target /v1/usermgmt/batch/users. Tango disambiguates based on whether business_unit is present in the request. Confirm there’s no separate non-BU endpoint.
  • Status endpoint missing /v1 prefix — same anomaly as the BU variant.
  • Same caveats apply for the GENERAL_USER extra-fields behavior, default-resolution rules, and unfilled lookup tables in the Appendix.

​
Changelog