Ramp API Contract Upgrade

Overview

Treat documentation or schema drift as a migration. Diff the exact contracts, map affected business behavior and stored data, then canary a reviewed artifact without silently changing scopes or writes.

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 publishes a changelog, OpenAPI schema, guide exports, and API reference; each may reveal a different class of impact.
• Legacy Cards endpoints are being deprecated for virtual-card management in favor of Funds and Cards (Virtual).
• Adding configured scopes does not update an existing token; new tokens are required.
• Unknown fields may be accepted or rejected by endpoint, so compatibility must be tested against the current schema.