Connector Improvement: Ramp API to use the new Limits API
CompletedRamp has recently announced that they will be deprecating their Cards API and moving to Limits API. When working with several of our end users, the data in the Ramp UI (leveraging the Limits API) is very different than the data in the Fivetran tables, which seem to more closely match what is available through the Cards API.
For example, Reimbursements in the Cards API live in a completely separate space that cards and important card metadata, like display name, cardholder, etc. It makes joins very difficult, especially when reimbursements are so common - accounting for the majority of card spend at our client company. As is, our client really isn't getting any value from the ramp data via Fivetran, even though they urgently want it.
-
Official comment
Hi Kelsey,
Just wanted to provide an update on this improvement request.
Ramp Connector now supports LIMITS data.
You can refer ERD for more information: https://fivetran.com/connector-erd/ramp
Let us know if you face any issues with this.
Thank You,
Vishal
Please sign in to leave a comment.
Comments
1 comment