> For the complete documentation index, see [llms.txt](https://docs.giize.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.giize.com/product-docs/api-reference/staging-api-overview.md).

# Staging API Overview

## What Was Collected

The staging docs site was accessed live after login and its source documents were extracted from:

```
https://request-staging.vng.vn/doctool/client_data/entities/*.txt
```

## Current Snapshot

* valid entity doc files: `165`
* failed file: `Hours.txt` returned `404`
* total documented operations: `941`
* total documented attributes: `1448`

## What This Means

The staging docs are not just a menu shell. They expose a large internal contract surface that can be mined reliably once logged in.

## Common Contract Patterns

* `GET`, `POST`, `PUT`, `DELETE`
* payloads via `input_data`
* JSON responses
* docs mention both `authtoken` and logged-in session usage

## Main Domain Families

* Request
* Problem
* Change
* Project
* Release
* Solutions
* Contract
* Admin metadata
* Purchase
* Approvals
* Task
* Worklog
* Device Registration
* Asset
* CMDB
* Reports
* Announcements
* Software

## Relationship To Production Notes

Use staging docs to understand breadth.

Use `SDP API` and the source note in `document/api_sdp.md` to understand what is already verified in real project flows.