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

# Box

> Box Scenario seeding parameters, nested fields, and examples

Use `box` in `twins` and put this configuration under `seed_config.box`.

Box with users, folders, and files.

## Example seed

This is the complete Scenario request body for [creating a Scenario](https://docs.argalabs.com/api-reference/post-create-a-scenario.md). You can also import it with `arga test-runner scenarios import --file scenario.json`.

```json theme={null}
{
  "name": "Box eval fixture",
  "twins": [
    "box"
  ],
  "seed_config": {
    "box": {
      "users": [
        {
          "name": "User Name",
          "login": "user@example.com"
        }
      ],
      "folders": [
        {
          "name": "Folder Name",
          "parent_id": "0",
          "files": [
            {
              "name": "file.txt",
              "content": "file content",
              "mime_type": "text/plain"
            },
            {
              "name": "photo.jpg",
              "mime_type": "image/jpeg"
            }
          ]
        }
      ]
    }
  }
}
```

## Parameters

The following fields belong directly inside `seed_config.box`. Required nested fields are marked in their tables. Provider-native objects can contain service-specific fields beyond the representative record shapes below.

| Parameter | Type | Description |
| - | - | - |
| `users` | `object[]` | Users fixtures in provider-native format. |
| `folders` | `object[]` | Folders fixtures in provider-native format. |

## Resource fields

These tables describe the record shapes used by the example. Keep native field names and casing. Map keys such as property names, IDs, and metadata keys are supplied by your fixture.

### `users[]`

| Parameter | Type | Description |
| - | - | - |
| `name` | `string` | Human-readable name. |
| `login` | `string` | Login. |
| `role` | `string` | Role. |

### `folders[]`

| Parameter | Type | Description |
| - | - | - |
| `name` | `string` | Human-readable name. |
| `parent_id` | `string` | Parent id. |
| `files` | `object[]` | Files fixtures in provider-native format. |

### `folders[].files[]`

| Parameter | Type | Description |
| - | - | - |
| `name` | `string` | Human-readable name. |
| `content` | `string` | Text content. |
| `mime_type` | `string` | Mime type. |
| `content_base64` | `string` | Content base64. |
| `data` | `string` | Data. |
| `mimeType` | `string` | MimeType. |

## API coverage and limitations

**Twin name:** `box`

**Supports**

* Box v2.0 file and folder APIs, including list, upload, download, update, delete, search, and event streams.
* OAuth token exchange, refresh tokens, developer tokens, and downscoped token restrictions.
* Webhook registration, signed webhook delivery attempts, retries, replay, and admin inspection.
* Unified storage and HRIS bridge behavior for apps that reach Box through Unified.

**Known limitations**

* Preview, thumbnail, transform/export, and advanced enterprise permissions are approximated rather than fully implemented.
* Unsupported webhook triggers, folder sort keys, search sort keys, event stream types, or downscope scopes return structured `400` or `403` responses.
* Arbitrary MIME uploads are stored as opaque content when the twin does not model preview or conversion behavior.

**MCP tools:** `get_twin_catalog`, `provision_twins`, `start_url_validation`, `get_validation_results`.

See [Scenario seeding](https://docs.argalabs.com/twins/seeding.md) for saving, provisioning, and resetting fixtures.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.