Tango Lease Outbound API
Generated fromTango Lease Outbound API Integration Design Specification V0.7.docxin SharePoint folder02 Lease Integrations. OAS spec:lease-outbound.yaml
Overview
Async delta REST API: client retrieves lease records that were created or updated since the last integration run. Information from Basic Info, Options & Terms, Contacts, Recurring Costs, and Obligations tabs is included. Two-call pattern withgu_id and pagination.
Owner: Tango Analytics
Spec version: 0.7
Status: Draft (auto-generated — needs review). Field-level mapping not extracted from source.
Base URLs
Authentication
Headersx-client + x-api-key.
Endpoints
GET /v1/leasemgmt/delta/leases
Response — 200 OK
GET /v1/batch/status?gu_id=...&page_no=...
Null fields omitted. Default page_no = 1, page size 5000.
Integration logic
- Delta semantics: only records updated after the last integration run are returned.
- Lookup behavior: lookup values displayed in the UI are exported when
extattribute1is not populated.
Data model
⚠ The source design doc does not include a complete field-level data-mapping table. Onlylease_num, name, and acct_type_code appear in the truncated response sample. The Tango Lease entity is rich (Basic Info, Options & Terms, Contacts, Recurring Costs, Obligations, etc.), and the full payload structure must be inferred from the production API or another source.
The YAML defines LeaseRecord with additionalProperties: true and the three documented fields.
Open Questions / Assumptions
- Complete field list is missing — re-source from a doc revision that includes the data-mapping table, or extract from the production API surface.
- Tab-by-tab content (Options & Terms, Recurring Costs, Obligations, etc.) is mentioned but not specified in the extracted text.
-
acct_type_code: present in the sample but not described. - Lookup behavior with
extattribute1is described but not enumerated for which fields/lookups it applies to. - Pagination page size 5000 (non-configurable per the doc).

