Skip to main content
Use ramp in twins and put this configuration under seed_config.ramp. Ramp finance workspace: business, departments, locations, entities, users, spend programs, funds, virtual/physical cards, transactions, receipts, vendors, bills, reimbursements, and accounting data, purchase orders, item receipts, unified requests, vendor agreements/credits, tax and inventory fields, custom records/matrices, approvals, bank and travel reports, and AI usage.

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

departments[]

locations[]

entities[]

users[]

funds[]

virtual_cards[]

transactions[]

vendors[]

draft_bills[]

draft_bills[].line_items[]

Typed configuration objects

Named object types in the parameter table use these fields.

FailureRule

OAuthClient

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