Ramp

Ramp is a finance automation platform that unifies corporate cards, expense management, bill pay, and vendor management to help finance teams control spend and close the books faster. The Ramp Developer API exposes read access to transactions, bills, vendors, cards, users, reimbursements, and other account data, making it possible to sync corporate spend and accounts payable information into external reporting, analytics, and ERP systems.

Power end-to-end data operations for your Ramp API with Nexla. Our bi-directional Ramp connector is purpose-built for Ramp, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Ramp or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Ramp workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

Ramp uses the OAuth 2.0 Client Credentials grant for API access, so your Nexla connection authenticates directly as an application — there is no end-user login or redirect step.

To obtain your Ramp API credentials:

1. Sign in to Ramp as a workspace admin (or a user with developer permissions), then navigate to Settings > Developer.

2. Click Create New App to register a new API application. Give it a descriptive name (e.g., "Nexla Integration") and accept the Ramp API Terms of Service.

3. Under Grant Types, click Add new grant type and select Client Credentials. This is the server-to-server flow Nexla uses to obtain access tokens without a user login step.

4. Under Scopes, click Configure allowed scopes and select the read scopes needed for the data this connector will sync — for example transactions:read, bills:read, and vendors:read. Ramp scopes generally follow a <resource>:read naming pattern, so add the scope for each resource (transactions, bills, vendors, users, cards, reimbursements, departments, locations, entities) you plan to bring into Nexla. Only grant the scopes you actually need.

5. Save the app configuration, then copy the Client ID and Client Secret that Ramp generates. The Client Secret is displayed only once, so store it securely before navigating away from the page.

Nexla exchanges the Client ID and Client Secret for a short-lived bearer token by calling Ramp's token endpoint and automatically refreshes the token as it expires. If a Client Secret is ever exposed, revoke and regenerate it immediately from Settings > Developer in Ramp — see Ramp's guidance on what to do if OAuth credentials are leaked. For the full API reference, see the Ramp Developer API documentation and the Accessing the Developer API guide.

Authenticate

Credentials required

Authenticate using OAuth 2.0 Client Credentials flow with Ramp API

Field	Required	Secret	Description
Client ID	Yes	No	OAuth Client ID from your Ramp Developer App
Client Secret	Yes	Yes	OAuth Client Secret from your Ramp Developer App
OAuth Scopes	Yes	No	Space-separated OAuth scopes (e.g., transactions:read bills:read vendors:read)

Create a credential in Nexla

1. After selecting the data source type, click the Add Credential tile to open the Add New Credential overlay.

New Credential Overlay – Ramp

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. In the Client ID field, enter the OAuth Client ID from your Ramp Developer App that you obtained in Prerequisites. This is the unique identifier for your registered Ramp application.

4. In the Client Secret field, enter the OAuth Client Secret from your Ramp Developer App. This value is used together with the Client ID to obtain an access token and must be kept confidential.

   If your Client Secret is compromised, revoke and regenerate it immediately from Settings > Developer in your Ramp account. The Client Secret provides access to your Ramp account data and should be treated as sensitive information.

5. In the OAuth Scopes field, enter the space-separated list of scopes your Nexla app was granted in Ramp, for example transactions:read bills:read vendors:read. Include a scope for every Ramp resource this connector will read from.

   The scopes entered here must match (or be a subset of) the scopes configured for the app under Settings > Developer > [Your App] > Scopes in Ramp, or requests to endpoints outside those scopes will be rejected. For detailed information about registering apps, grant types, and scopes, see the Ramp Developer API documentation.

6. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Ramp connector tile, then select the credential that will be used to connect to Ramp, and click Next; or, create a new Ramp credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Ramp endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

Get Transactions

This endpoint template retrieves card spend transactions from your Ramp account, including transaction amounts, merchants, card and cardholder details, and accounting/category data. Use this template to sync corporate card spend into expense reporting, accounting, or spend-analysis systems.

• This endpoint automatically retrieves all transactions accessible to the OAuth scopes on your credential. The endpoint uses next-URL pagination, and Nexla automatically follows the page.next link in each response to fetch subsequent pages.

For detailed information about the transaction data model and available query parameters, see the Ramp API Documentation.

Get Bills

This endpoint template retrieves vendor invoices and bills from your Ramp Bill Pay account, including bill amounts, statuses, due dates, and associated vendor information. Use this template to sync accounts payable data into ERP or accounting workflows.

• This endpoint automatically retrieves all bills accessible to the OAuth scopes on your credential. The endpoint uses next-URL pagination, and Nexla automatically follows the page.next link in each response to fetch subsequent pages.

For detailed information about the bill data model and available query parameters, see the Ramp API Documentation.

Get Vendors

This endpoint template retrieves the supplier/vendor directory maintained in your Ramp account, including vendor names, contact details, and remit-to information. Use this template to keep an external vendor master list in sync with Ramp.

• This endpoint automatically retrieves all vendors accessible to the OAuth scopes on your credential. The endpoint uses next-URL pagination, and Nexla automatically follows the page.next link in each response to fetch subsequent pages.

For detailed information about the vendor data model and available query parameters, see the Ramp API Documentation.

Get Users

This endpoint template retrieves employee and cardholder records from your Ramp account, including names, email addresses, department, location, and role information. Use this template to sync user and employee data for reporting or identity-matching purposes.

• This endpoint automatically retrieves all users accessible to the OAuth scopes on your credential. The endpoint uses next-URL pagination, and Nexla automatically follows the page.next link in each response to fetch subsequent pages.

For detailed information about the user data model and available query parameters, see the Ramp API Documentation.

Get Cards

This endpoint template retrieves virtual and physical card records from your Ramp account, including card status, spend limits, and the cardholder each card is assigned to. Use this template to monitor card issuance and spend limits from outside Ramp.

• This endpoint automatically retrieves all cards accessible to the OAuth scopes on your credential. The endpoint uses next-URL pagination, and Nexla automatically follows the page.next link in each response to fetch subsequent pages.

For detailed information about the card data model and available query parameters, see the Ramp API Documentation.

Get Reimbursements

This endpoint template retrieves employee expense reimbursement requests from your Ramp account, including amounts, statuses, and submitting employee details. Use this template to sync out-of-pocket expense reimbursements into accounting or payroll systems.

• This endpoint automatically retrieves all reimbursements accessible to the OAuth scopes on your credential. The endpoint uses next-URL pagination, and Nexla automatically follows the page.next link in each response to fetch subsequent pages.

For detailed information about the reimbursement data model and available query parameters, see the Ramp API Documentation.

Get Departments

This endpoint template retrieves the organizational department structure configured in your Ramp account. Use this template to sync department names and IDs for cost-center reporting or spend attribution.

• This endpoint automatically retrieves all departments accessible to the OAuth scopes on your credential. The endpoint uses next-URL pagination, and Nexla automatically follows the page.next link in each response to fetch subsequent pages.

For detailed information about the department data model and available query parameters, see the Ramp API Documentation.

Get Locations

This endpoint template retrieves the locations configured in your Ramp account, which Ramp uses for spend policy and approval routing. Use this template to sync location data for reporting or policy administration outside Ramp.

• This endpoint automatically retrieves all locations accessible to the OAuth scopes on your credential. The endpoint uses next-URL pagination, and Nexla automatically follows the page.next link in each response to fetch subsequent pages.

For detailed information about the location data model and available query parameters, see the Ramp API Documentation.

Get Business Entities

This endpoint template retrieves the business entities configured in a multi-entity Ramp account, such as subsidiaries or legal entities. Use this template to sync entity data for consolidated or entity-level accounting.

• This endpoint automatically retrieves all business entities accessible to the OAuth scopes on your credential. The endpoint uses next-URL pagination, and Nexla automatically follows the page.next link in each response to fetch subsequent pages.

For detailed information about the business entity data model and available query parameters, see the Ramp API Documentation.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

Ramp data sources can also be manually configured to ingest data from any valid Ramp Developer API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom query parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

Ramp API endpoints are rooted at https://api.ramp.com/developer/v1/{resource} and use the GET method for read access. For the Response Data Path, use $.data[*] to extract the array of records returned by most endpoints. Ramp uses next-URL pagination — set the pagination JSONPath to $.page.next.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Ramp data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.