Articles in this section

Set up a connection to Ramp

Ramp is a multinational financial technology software that offers corporate charge cards, expense management, and bill payment.

Set up a connection

After you start the connection, configure it in the Create connection panel and complete all of the required * authentication settings:

Setting

Instructions

Name your connection * 

Enter a clear and distinguishable name.

Throughout integrator.io imports and exports, you will have the option to choose this new connection. A unique identifier will prove helpful later when selecting it from a list of the connections in your account.

Environment * 

Select your Ramp account environment:

  • Production: if your account URL is https://api.ramp.com.

  • Sandbox: if your account URL is https://demo-api.ramp.com.

OAuth 2.0 client * 

Select the OAuth 2.0 client that stores the client ID and client secret provided to you by Ramp.

To add an OAuth 2.0 client and configure your credentials, click the plus (+) button. Click the edit button to modify a selected OAuth 2.0 client. For more information, see Create an OAuth 2.0 iClient resource.

How to retrieve the client ID and client secret  

Scopes * 

Scopes are OAuth 2.0 permissions that Ramp defines to limit access to your account.

How to configure scopes   

Tip

This connector documentation describes only the settings shown for the Simple view. For the corresponding HTTP settings, see OAuth 2.0 auth universal connector documentation.

How to retrieve the client ID and client secret

  1. Sign in to your Ramp developer account.

  2. Click Create new app.

  3. Enter an App name and Description.

  4. Click Create App.

  5. Copy the Client ID.

  6. Copy the Client secret.

How to configure scopes

  1. Click Scope.

  2. To access all of the scopes in the API, click the » button.

    – or – 

    Check the scopes you want to add and click the > button.

  3. Click Save.

Additional references

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Article is closed for comments.