Ramp API Error Triage

Overview

Turn a failing request into a sanitized, reproducible diagnosis. Separate permanent request or authority failures from transient service conditions before retrying anything.

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 returns standard HTTP status codes and may include error_v2.error_code, additional_info, and a user-facing message.
• Every API response includes x-trace-id; preserve it for correlation and support without logging authorization or sensitive payloads.
• 401 indicates a missing, expired, or invalid token; 403 indicates a valid token without sufficient scope or resource authority.
• 429 and 5xx may be retried with bounded exponential backoff; 504 means the request crossed Ramp's 60-second timeout.