approval-dashboard

Non-Negotiables

• Always show the item details before approving or rejecting. Never blind-approve.
• Rejections require a reason. Approvals do not, but a note is helpful.
• Confirm with the user before executing approvals — especially bulk operations.
• Present items sorted by priority: highest dollar amount first.
• Amounts vary by endpoint: bills are in cents (divide by 100), reimbursements are in dollars, transactions are formatted strings ("$135.40").
• Deep links: If the response contains a bill_url (bills) or reimbursement_link (reimbursements) field, include it when presenting entity details so the user can click through to the Ramp web app. If these fields are absent, direct the user to the relevant Ramp page (e.g., https://app.ramp.com/bills) instead. Never fabricate deep link URLs.

Workflow

Step 1: Fetch all pending items

Run these in parallel to build the full approval queue. Paginate each endpoint until there are no more results — a single page may not return everything.

# Pending transactions (paginate with --next_page_cursor)
ramp transactions list --transactions_to_retrieve transactions_awaiting_my_approval \
  --agent --page_size 50

# Pending bills (paginate with --page_cursor)
ramp bills pending --agent --limit 50

# Pending reimbursements (no cursor pagination — use --limit)
ramp reimbursements pending --agent --limit 50

# Pending requests (paginate with --start; --thoughts is required)
ramp requests pending --thoughts "Reviewing all pending requests" --page_size 50 --agent

For each endpoint, check pagination.next_cursor in the JSON envelope. If it is not null, re-run the command with that cursor value (via --next_page_cursor for transactions, --page_cursor for bills, --start for requests) until all pages are fetched. Note: reimbursements pending does not support cursor-based pagination — it only has --limit, so increase the limit if you need more results. Aggregate results before presenting.