Skip to main content

​
Tango Budget Outbound API

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

​
Overview

Async delta REST API: client retrieves newly-approved or updated project-budget records from Tango. 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 newly-approved budgets or updates after the last integration run are included.
  • transaction_type = NEW for newly approved budgets; UPDATE for changes to existing.
  • Page size 5000; first page returned if page_no is omitted.
  • Null fields are omitted from response JSON.

​
Data model

​
Open Questions / Assumptions

  • Integration type header inconsistency — header says space Area outBOUND api but the document is clearly about budgets (title, content, fields). Assumed a stale copy-paste from a different spec template.
  • milsetone_name typo — should likely be milestone_name. Preserved verbatim.
  • task_number typed NUMBER in mapping but sample is TSK125 (alphanumeric). Schema uses string.
  • brand_name typed NUMBER in mapping but sample is Tango (string). Schema uses string.
  • No validations listed in the source doc.
  • Lookup codes are <TBD> in Appendix.

​
Changelog