Ramp Sandbox Development Loop

Overview

Keep the default loop deterministic and offline, then use Ramp sandbox for the smallest behavior that needs vendor execution. Make environment resolution visible and fail closed before any local write can reach production.

Prerequisites

• Identify the Ramp application, environment, business entities, affected data and workflows, accountable owner, and rollback boundary.
• Read references/official-docs.md and re-check endpoint schemas, scopes, limits, and support status before a live operation.
• Use synthetic fixtures or Ramp sandbox until production access and business effects are explicitly approved.
• Prepare approved secret storage and a sanitized evidence location.

Current Contract

• Ramp sandbox uses https://demo.ramp.com for the UI and https://demo-api.ramp.com for Developer API calls.
• Sandbox has no real money movement and supports demo actions for creating transactions and advancing selected bill or reimbursement states.
• Sandbox permissions still affect demo actions and API behavior.
• The official OpenAPI document provides request and response schemas for local fixtures and contract checks.