> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tangoanalytics.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Space area outbound

# Tango Space Area Outbound API

> Generated from `Tango Space Area Outbound API Integration Design Specification V1.0.docx` in SharePoint folder `03 Space Integrations`.
> OAS spec: [`space-area-outbound.yaml`](./space-area-outbound.yaml)

## Overview

Async **delta** REST API: client retrieves Space Area records updated in Tango since the last integration run. Two-call pattern with `gu_id` and pagination (5000/page).

**Owner:** Tango Analytics
**Spec version:** 1.0
**Status:** Draft (auto-generated — needs review)

## Endpoints

| Method | Path | Summary |
| - | - | - |
| GET | `/v1/spacemgmt/delta/areas` | Initiate delta export. |
| GET | `/v1/batch/status?gu_id=...&page_no=...` | Retrieve paginated records. |

## Integration logic

* Delta API; updates to `space_area_id`, `building_id`, or `floor_id` do NOT trigger export.
* Null fields omitted from response.

## Data model

| Field | Type | Notes |
| - | - | - |
| `space_area_id` | NUMBER | Tango internal area ID |
| `building_id` | NUMBER | |
| `building_number` ⚠ | NUMBER | Source typed NUMBER but sample `"1234"` (string) |
| `floor_id` | NUMBER | |
| `floor_number` ⚠ | NUMBER | Source typed NUMBER; sample `"05"` (leading-zero string) |
| `property_number` ⚠ | NUMBER | Source typed NUMBER; sample `"REGION 2"` (string) |
| `area_name` / `area_number` | VARCHAR | |
| `area_type` | VARCHAR | e.g., `Flexible Seating` |
| `mac_enabled` / `is_flexible_seating` / `is_shift_seating` | VARCHAR | Y/N |
| `lease_rentable_sf` | NUMBER | |
| `allocation_type` | VARCHAR | e.g., `People Allocation` |
| `number_of_shifts` ⚠ / `shift_length` ⚠ | NUMBER | Source typed VARCHAR; samples are numeric |
| `country` / `status` | VARCHAR | |
| `space_count` / `headcount` / `max_occupancy` / `flex_occupancy` / `current_occupancy` / `available_occupancy` | NUMBER | |
| `last_update_date` | TIMESTAMP | |
| `last_updated_by` | VARCHAR | |

## Open Questions / Assumptions

* [ ] **Type mismatches across `building_number` / `floor_number` / `property_number`** — mapping says NUMBER but samples are strings (some with leading zeros / alphanumeric like `REGION 2`). Schema follows mapping; runtime may emit strings.
* [ ] **`number_of_shifts` / `shift_length` typed VARCHAR but samples are numeric** (`2`, `8`). Schema uses NUMBER.
* [ ] **`status` allowed values not enumerated** — sample is blank.
* [ ] **Source version 0.9 dated `07/29/2205`** — clearly a typo (`2025`). Cosmetic only.
* [ ] **`available_occupancy` sample `0.3`** suggests fractional occupancy; confirm semantic.

## Changelog (compressed)

| Ver | Date | Description | Author |
| - | - | - | - |
| 0.1–0.9 | 2022-2025 | (see source doc) | Various |
| 1.0 | 04/22/2026 | Updated API architecture diagram | Alpna Bansal |