Ramp

Overview

The Ramp connector reads from the Ramp Developer API on a schedule. Each cleared transaction, reimbursement or bill becomes a typed event with the merchant, amount, card holder and accounting codes attached, and every poll shows up in the trace.

Finance and IT teams use it to ask for a missing receipt in Slack, to post cleared spend to NetSuite and to terminate a departing employee's cards when Okta deactivates their account.

Supported objects

• Card transactions, reimbursements and bills

• Users, cards, spend limits and departments

• Accounting fields and custom fields set in Ramp

How polling works

Tessel calls the list endpoints every two minutes with a from_date cursor and follows the next link until the page is empty. Only records changed since the last poll start runs. Tokens come from the client credentials grant and refresh on their own.

curl https://api.ramp.com/developer/v1/transactions \
  -G \
  -d from_date=2026-10-06T09:00:00Z \
  -d state=CLEARED \
  -d page_size=100 \
  -H "Authorization: Bearer $RAMP_TOKEN"

curl https://api.ramp.com/developer/v1/transactions \
  -G \
  -d from_date=2026-10-06T09:00:00Z \
  -d state=CLEARED \
  -d page_size=100 \
  -H "Authorization: Bearer $RAMP_TOKEN"

curl https://api.ramp.com/developer/v1/transactions \
  -G \
  -d from_date=2026-10-06T09:00:00Z \
  -d state=CLEARED \
  -d page_size=100 \
  -H "Authorization: Bearer $RAMP_TOKEN"

Pagination

Ramp pages results with a cursor rather than offsets, so new records never shift a page. Tessel stores the last cursor per object type and resumes from it after a pause.

Permissions needed

Create a developer app in Ramp for Tessel. It needs read scopes for the objects your triggers watch. Write scopes are only required for limit and card actions.

• transactions:read, reimbursements:read and bills:read

• users:read and cards:read for lookups

• limits:write and cards:write only if you use those actions