Inventory
Inventory is SmartAPI's model of your API: the endpoints discovered from your sources, the fields they exchange, and the relationships between them.
API Test Generation generates against a published inventory version, so this page is where you decide what generation is allowed to see.
Until a source has been analyzed the page reads No published inventory yet, with a shortcut to File Management.
Versions and scope
A workspace keeps a history of inventory versions. The scope controls at the top choose which one you are looking at:
| Control | What it selects |
|---|---|
| Source | One source file, or all of them |
| File version | Which version of that file. Endpoints absent from the snapshot are marked Not included in this inventory version |
| Inventory version | The published revision, labelled Version <n> and marked Current for the newest |
Each inventory version keeps the file versions that were analyzed together, so an older version is a faithful snapshot rather than a filtered view of today's data.
Generating from an older snapshot omits endpoints added later. The generation scope picker says so when the version you chose is not the current one.
The tabs
| Tab | What it shows |
|---|---|
| Endpoints | Every operation, as a service tree or a flat table. Filter by method, service, review status, or match confidence |
| Service Map | How this version's services sit around the API, as a table or a draggable graph |
| Flow | The main flow through the API. Filter by service to follow one service's incoming and outgoing dependencies |
| Relations | Inferred and edited dependencies between endpoints, with the fields that bind them |
| Security Schemes | The declared schemes these endpoints use, as cards or a table |
A summary strip above the tabs counts Endpoints, Services, Relations, and Awaiting Review — proposed relations that nobody has confirmed or rejected yet.
Reviewing proposed relations
Analysis proposes relationships between endpoints and scores how confident it is. Each proposal can be confirmed or rejected, individually or in bulk, and strong matches can be confirmed together.
Reviewing them matters: relations are what let generation chain requests into a workflow instead of testing each endpoint in isolation.
Editing and publishing
Changes are made in a draft rather than against the published version. A workspace holds at most one editable draft, and the page moves onto it with your first saved change.
From the Endpoints and Relations tabs you can add an endpoint or a relation, edit an operation's fields, contract, and security, and rename or delete a service.
| Action | Effect |
|---|---|
| Create draft | Starts an editable copy of the published version |
| Save and Publish | Publishes the draft as a new inventory version |
While a draft has unpublished work the page says This draft has changes that are not published yet.
Deleting an endpoint or renaming a service changes the draft only. Earlier versions and already-saved scenarios keep working — publishing applies the change from that version onward.
Only users who can update collections see the edit actions; a historical snapshot stays read-only for everyone.
Next Steps
- API Test Generation — Generate against the version you published here
- File Management — Upload and re-analyze the sources behind the inventory
- SmartAPI Quick Start — The whole path from source to saved scenario
