Skip to main content

Tango AR Outbound API

Generated from Tango AR Outbound API Integration Design Specification V1.0.docx in SharePoint folder 02 Lease Integrations. OAS spec: ar-outbound-api.yaml

Overview

Async REST API: client GETs approved receivables (billings) from Tango. Two-call pattern with gu_id and paginated retrieval. Page size 5000. Owner: Tango Analytics Spec version: 1.0 Status: Draft (auto-generated — needs review)

Base URLs

Authentication

Headers x-client + x-api-key.

Endpoints

GET /v1/leasemgmt/receivables

Optional query params: calendar_year, calendar_month, country, financial_group. Response — 200 OK

GET /v1/batch/status?gu_id=...&page_no=...

Default page_no = 1, page size 5000. Null fields are omitted from the JSON.

Data model (required ✅)

Open Questions / Assumptions

  • Source typo: the doc mapping lists segt2_gl instead of seg2_gl. Preserved verbatim in the schema; confirm whether the real Tango field name is seg2_gl.
  • year / month typing mismatch: response example shows "year": "2020" (string), the mapping says VARCHAR, but the comment says “Calendar year/month” implying numeric. Schema follows mapping (string).
  • Status response shape for this endpoint is documented less completely than AP Outbound’s — assumed the same paginated header pattern.
  • Lookup codes are <TBD> in Appendix.

Changelog