Studio File

The Studio File discovers assets from a structured file — such as a CSV — uploaded to vScope’s local storage. It is part of Studio, which extends discovery to sources without native probes.

Use it when asset data exists in a flat file or periodic export that should be part of your inventory: custom hardware lists, SaaS seat exports, offline device registers, or any other structured data without a dedicated integration. Imported assets are available in tables, dashboards, Tracker, and billing just like any other asset.

Prerequisites

A vScope account with API access.
A CSV file with at least one column that can serve as a unique asset identifier per row.
A Studio File custom config — contact customersuccess@vscope.net for a template.

Steps

1. Prepare your CSV

The first row is treated as column headers. Column names are referenced by name in the custom config, so keep them consistent across updates.

id,email,full name
1,alice.johnson@example.com,Alice Johnson
2,bob.smith@example.com,Bob Smith
3,carol.white@example.com,Carol White

2. Upload the file

POST /api/rest/storage?type=CSV
Content-Type: multipart/form-data

file: <file contents>

Response:

{
  "reference": "c1a80d39-e32d-4c7f-bc42-4af218ca7fa6",
  "size": 1024,
  "type": "CSV",
  "lastAccessed": 1748908800000
}

Copy the reference UUID — it goes into the custom config and never changes for this file.

3. Configure the custom config

The integration requires a custom config that maps the CSV structure to vScope assets. Place the reference UUID from step 2 into the config, then assign it to the integration in vScope.

Config templates for Studio File are available from customersuccess@vscope.net.

4. Assign the config to the probe in vScope

In vScope, navigate to Discovery Manager and assign the custom config to the Custom File target.

5. Run discovery and verify

Trigger a discovery run. Each row in the CSV becomes a Studio Asset in vScope. Use Tables with a Found By: Custom File filter to review the imported assets.

Updating file contents

To replace the file data without changing the reference UUID — so existing configs continue to work without any changes:

PUT /api/rest/storage/c1a80d39-e32d-4c7f-bc42-4af218ca7fa6?type=CSV
Content-Type: multipart/form-data

file: <updated file contents>

The probe picks up the new data on its next run.

Removing a file

Before deleting, remove the reference from any custom configs. If the file is missing and the config treats it as required, the run is marked as failed.

DELETE /api/rest/storage/c1a80d39-e32d-4c7f-bc42-4af218ca7fa6