​

Tango Lease Invoices Outbound API

Generated from Tango Lease Invoices Outbound API Integration Design Specification V0.3.docx in SharePoint folder 02 Lease Integrations. OAS spec: lease-invoices-outbound.yaml

​

Overview

Async REST API: client fetches approved lease invoices from Tango. Each invoice header contains a lines array of individual payments. Two-call pattern with gu_id and pagination (5000/page). Null fields are omitted from the JSON. Owner: Tango Analytics Spec version: 0.3 Status: Draft (auto-generated — needs review)

​

Base URLs

​

Authentication

Headers x-client + x-api-key.

​

Endpoints

​

GET /v1/leasemgmt/invoices

Optional query params: calendar_year, calendar_month, country, financial_group.

​

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

Returns paginated invoice headers; each header has a lines array. Null fields omitted.

​

Integration logic

• Only approved batches and invoices on Active leases are returned.
• Invoices land in Lease Financials → Lease Invoices tab in Tango once generated.
• One-time invoices are created from the Lease Invoices tab.
• After approval, invoices are picked up by this API.
• Same gu_id may be polled multiple times.

​

Data model — Invoice Header (required ✅)

​

Data model — Invoice Line (required ✅)

​

Open Questions / Assumptions

• No synchronous error response shape documented at the initial GET — assumed same as other Tango APIs.
• payext1 is missing from the field list (jumps to payext2); confirmed absent in the source mapping.
• Status path doc shows only 2 columns of method/asynch/headers (compared with 3 elsewhere) — likely a formatting issue in source; assumed same flow.
• exchange_rate typed VARCHAR — likely numeric. Confirm.
• Lookup codes are <TBD> in Appendix.

​

Changelog