At a glance
- Availability: Experimental (how to enable).
- Authentication: OAuth 2.0 (client credentials).
- Connection: Veryfront obtains machine-to-machine tokens from the client ID and secret in the project’s environment variables.
- Provider documentation: Authentication reference.
Credentials
Set these per environment. See Connect an integration.Setup
- Get a Ramp account or sandbox: Sign up at https://ramp.com, or request Sandbox access from Ramp to build without a live account. The sandbox has the same API surface with test data: app at https://demo.ramp.com, API at https://demo-api.ramp.com.
- Create a developer app: In the Ramp dashboard go to Company → Developer (admin access required) and click Create New App. Copy the Client ID and Client Secret.
- Enable the Client Credentials grant and scopes: In the app settings, under Grant types add Client Credentials, then under Scopes configure the allowed scopes: transactions:read, cards:read, users:read, reimbursements:read.
- Set environment variables: Add RAMP_CLIENT_ID and RAMP_CLIENT_SECRET to your .env.
- Verify access: Run List Transactions. Access tokens are minted automatically from https://api.ramp.com/developer/v1/token using HTTP Basic auth with your client credentials; the requested scopes are sent in the token request.
Provider notes
- Sandbox and production require separate apps - create one app in each environment. This connector targets production (api.ramp.com); for sandbox testing point a copy at demo-api.ramp.com with sandbox app credentials.
- Scopes are configured on the app and requested at token time; only request the scopes you need.
- List endpoints paginate with a page.next cursor - pass the last item’s ID as the start parameter for the next page.
Tools
Verify the connection
Call a read tool such asramp__list_transactions with arguments for your account. Confirm that the result comes from the intended account or workspace before enabling write tools.