Skip to main content
Use seismic in twins and put this configuration under seed_config.seismic. Seismic sales-enablement tenant with SCIM users and groups, TeamSites, Library and Workspace content, LiveSend deliveries, asynchronous LiveDoc generation, Programs and Planner work, reporting inputs, and signed webhooks.

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.seismic. Required nested fields are marked in their tables. Provider-native objects can contain service-specific fields beyond the representative record shapes below.

Seeding behavior

Tenant records support symbolic aliases and {"$ref":"alias.id"} references. Keep tenant IDs and related user/content IDs consistent across the fixture.

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.

tenants[]

tenants[].users[]

tenants[].users[].emails[]

tenants[].groups[]

tenants[].team_sites[]

tenants[].content_profiles[]

tenants[].custom_properties[]

tenants[].custom_properties[].domainOfValues[]

tenants[].library_content[]

tenants[].workspace_content[]

tenants[].live_sends[]

tenants[].live_docs[]

tenants[].programs[]

tenants[].tasks[]

tenants[].requests[]

tenants[].webhooks[]

Typed configuration objects

Named object types in the parameter table use these fields.

TenantSeed

WebhookSeed

See Scenario seeding for saving, provisioning, and resetting fixtures.