Ramp Migration Deep Dive

---
name: ramp-migration-deep-dive
description: "Ramp migration deep dive \u2014 corporate card and expense management\
  \ API integration.\nUse when working with Ramp for card management, expenses, or\
  \ accounting sync.\nTrigger with phrases like \"ramp migration deep dive\", \"ramp-migration-deep-dive\"\
  , \"corporate card API\".\n"
allowed-tools: Read, Write, Edit, Bash(npm:*), Bash(curl:*), Grep
version: 1.4.0
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>
tags:
- saas
- ramp
- fintech
- expenses
- corporate-cards
compatibility: Designed for Claude Code
---
# Ramp Migration Deep Dive

## Overview

Implementation patterns for Ramp migration deep dive using the Developer API with OAuth2 authentication.

## Prerequisites

- Completed `ramp-install-auth` setup

## Instructions

### Step 1: API Call Pattern

```python
import os, requests

# Obtain token
token_resp = requests.post(f"{os.environ['RAMP_BASE_URL'].replace('/v1','')}/v1/token", data={
    "grant_type": "client_credentials",
    "client_id": os.environ["RAMP_CLIENT_ID"],
    "client_secret": os.environ["RAMP_CLIENT_SECRET"],
})
access_token = token_resp.json()["access_token"]
headers = {"Authorization": f"Bearer {access_token}"}

cards = requests.get(f"{os.environ['RAMP_BASE_URL']}/cards", headers=headers)
print(f"Cards: {len(cards.json()['data'])}")
```

## Output

- Ramp API integration for migration deep dive

## Error Handling

| Error | Cause | Solution |
|-------|-------|----------|
| 401 Unauthorized | Expired token | Re-authenticate |
| 429 Rate Limited | Too many requests | Implement backoff |
| 403 Forbidden | Insufficient permissions | Check API app permissions |

## Resources

- [Ramp API Documentation](https://docs.ramp.com/)
- [Authorization](https://docs.ramp.com/developer-api/v1/authorization)

## Next Steps

See related Ramp skills for more workflows.