Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.

next
md 54 lines 4.37 KB
Rendered Raw
1 ## How do I set up custom OAuth credentials for Ramp?
2
3 Ramp has no Composio-managed app, so you register your own OAuth app in Ramp and use its credentials in the auth config. You need **Owner** or **Admin** access in Ramp to see the **Developer** page.
4
5 ### Create the Ramp app
6
7 1. Sign in to Ramp. Click your profile icon in the top-right corner and select **Settings**.
8 2. In the left sidebar, expand **Company** and click **Developer**.
9
10 ![Ramp Settings sidebar with Company expanded and Developer at the bottom](/images/toolkits/ramp/company-developer-menu.webp)
11
12 3. Under **My apps**, click **Create new app**. Enter an **App name**, accept the Developer Terms of Service, and click **Create app**.
13
14 ![Ramp Developer page with Create new app under My apps](/images/toolkits/ramp/developer-page.webp)
15
16 ![Ramp Create a new app dialog with the app name and Developer Terms checkbox](/images/toolkits/ramp/create-app-dialog.webp)
17
18 4. Ramp emails you a 6-digit verification code. Enter it and click **Verify**. The code expires after 5 minutes; click **Resend** for a new one.
19 5. Open the new app from **My apps**. Under **Redirect URIs**, click **+ Add new URI**, enter `https://backend.composio.dev/api/v1/auth-apps/add`, and click **Add**. It must exactly match the auth config's `oauth_redirect_uri` field, with no trailing slash.
20
21 ![Ramp My apps list showing the new app](/images/toolkits/ramp/my-apps-list.webp)
22
23 ![Ramp app detail page with the Composio redirect URI under Redirect URIs](/images/toolkits/ramp/redirect-uris.webp)
24
25 ![Ramp Add new URI dialog with the Composio redirect URI](/images/toolkits/ramp/add-redirect-uri.webp)
26
27 6. Under **Grant types**, turn on **Authorization code**, **Client credentials**, and **Refresh token**. Without the refresh token grant, connections stop working when the access token expires.
28
29 ![Ramp Grant types section with Authorization code, Client credentials and Refresh token turned on](/images/toolkits/ramp/grant-types.webp)
30
31 7. Copy the **Client ID**. Reveal the **Client secret** with the eye icon and copy it. If you lose it, click **Rotate client secret**, then update the auth config and reconnect affected accounts.
32 8. Under **Scopes**, click **Configure allowed scopes**, turn on the scopes you'll request, and click **Set**.
33
34 ### Create the auth config in Composio
35
36 1. In the [Composio dashboard](https://dashboard.composio.dev/~/project/auth-configs?utm_source=docs&utm_medium=content&utm_campaign=toolkits-ramp), go to **Auth Configs** → **Create** and select **Ramp**.
37 2. Paste the Client ID and Client Secret. Set the scopes to the same set you allowed on the Ramp app.
38 3. Check **Base URL** and **Authorization URL**. The defaults, `https://api.ramp.com/developer/v1` and `https://app.ramp.com/v1/authorize`, are for production Ramp accounts. If you registered the app on a Ramp demo account (your browser shows `demo.ramp.com`), use the `demo-api.ramp.com` and `demo.ramp.com` hosts instead. The wrong environment makes the token exchange fail.
39 4. Click **Create Auth Config**, then **Connect Account**. Review the permissions on Ramp's consent screen and click **Allow**. Confirm the account shows **Active** on the auth config's **Connected Accounts** tab.
40
41 See [custom auth configs](/docs/auth-configuration/custom-auth-configs) for the general flow.
42
43 ### Scopes
44
45 The default auth config requests read and write scopes across accounting, bills, cards, departments, limits, locations, memos, purchase orders, receipts, spend programs, users, and vendors, plus read access to transactions, statements, and other resources. Every scope the auth config requests must be allowed on the Ramp app, or authorization fails. Request only what your tools need, and remove from both sides anything you don't.
46
47 If you request `accounting:write` and the Ramp account already has an accounting provider connected, Ramp's consent screen warns that granting it may conflict. Remove `accounting:write` from both the Ramp app and the auth config if you don't need it.
48
49 ### Troubleshooting
50
51 - **`redirect_uri_mismatch`**: the redirect URI in Ramp doesn't exactly match the auth config's.
52 - **Token exchange fails**: the Base URL and Authorization URL point to the wrong Ramp environment (demo or production).
53 - **Connection goes inactive**: turn on the **Refresh token** grant type on the Ramp app, then reconnect from the auth config.
54 - **No Developer page**: ask a Ramp owner for the Owner or Admin role.