Skip to main content
Use dropbox in twins and put this configuration under seed_config.dropbox. Dropbox with folders and files.

​
Example seed

This is the complete Scenario request body for creating a Scenario. You can also import it with arga test-runner scenarios import --file scenario.json.

​
Parameters

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

​
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.

​
folders[]

​
folders[].files[]

​
API coverage and limitations

Twin name: dropbox Supports
  • Dropbox API v2 file operations including list, upload, download, copy, move, delete, search, revisions, tags, upload sessions, and batch operations.
  • Sharing APIs for shared links, shared folders, file members, file requests, file properties, and team/admin management.
  • Webhook delivery, event replay, seeded team members, a starter folder tree, and account tier-based storage quotas.
Known limitations
  • Some advanced Dropbox surfaces are represented through deterministic in-memory behavior rather than full production infrastructure.
  • Uploads that exceed configured account-tier quotas return an insufficient_space error.
  • Routes outside the modeled Dropbox API v2 surface may return structured non-support rather than a stateful response.
MCP tools: get_twin_catalog, provision_twins, start_url_validation, get_validation_results. See Scenario seeding for saving, provisioning, and resetting fixtures.