OVERALL CONTROL / 0.6-customer-control
Grades and scoring
Data access
25% of the overall score before applicability adjustment.
Scored answers and evidence
Read interface 7.5/10
Structured API for the declared product scope
Ramp Developer API / customer client credentials for transactions and scoped transaction edits; partner OAuth requires separate production approval.
Structured read interface for the declared product and resources
Ramp transaction API reference ↗
Structured read interface for the declared product and resources · Checked 2026-10-16
Bulk delivery 8.8/10
Batched or iterable API requests
Ramp Developer API / customer client credentials for transactions and scoped transaction edits; partner OAuth requires separate production approval.
List transactions; GET /developer/v1/transactions and paginated data collection
Ramp transaction API reference ↗
List transactions; GET /developer/v1/transactions and paginated data collection · Checked 2026-10-16
Query expressiveness 7.5/10
Fixed object or report retrieval
Ramp Developer API / customer client credentials for transactions and scoped transaction edits; partner OAuth requires separate production approval.
List transactions and transaction lookup; exact filter parameter coverage not scored
Ramp transaction API reference ↗
List transactions and transaction lookup; exact filter parameter coverage not scored · Checked 2026-10-16
Access cost barrier -
-
Ramp Developer API / customer client credentials for transactions and scoped transaction edits; partner OAuth requires separate production approval.
Reviewed entitlement documentation; minimum eligible plan and fixed route-specific access charges remain unresolved
Developer API Quickstart ↗
Reviewed entitlement documentation; minimum eligible plan and fixed route-specific access charges remain unresolved · Checked 2026-10-16
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility 5.0/10
Separate provider consent or partner agreement required
Ramp Developer API / customer client credentials for transactions and scoped transaction edits; partner OAuth requires separate production approval.
Partner integration; Ramp approves application before production customer OAuth
Ramp Developer API overview ↗
Partner integration; Ramp approves application before production customer OAuth · Checked 2026-10-16
Downstream permission -
-
Ramp Developer API / customer client credentials for transactions and scoped transaction edits; partner OAuth requires separate production approval.
Reviewed access documentation; applicable downstream processing, AI and redistribution terms not established
Developer API Quickstart ↗
Reviewed access documentation; applicable downstream processing, AI and redistribution terms not established · Checked 2026-10-16
External action
15% of the overall score before applicability adjustment.
Scored answers and evidence
Write interface 2.5/10
Named operations in a limited domain
Ramp Developer API / customer client credentials for transactions and scoped transaction edits; partner OAuth requires separate production approval.
Transaction update beta; PATCH /developer/v1/transactions/{transaction_id}
Developer API changelog: transaction update beta ↗
Transaction update beta; PATCH /developer/v1/transactions/{transaction_id} · Checked 2026-10-16
Custom application path 5.0/10
Approved third-party applications using fixed interfaces
Ramp Developer API / customer client credentials for transactions and scoped transaction edits; partner OAuth requires separate production approval.
Approved applications use the documented fixed API interfaces
Ramp Developer API overview ↗
Approved applications use the documented fixed API interfaces · Checked 2026-10-16
Continuity
15% of the overall score before applicability adjustment.
Scored answers and evidence
Refresh mechanism 7.5/10
Documented updated-since filters or webhooks
Ramp Developer API / customer client credentials for transactions and scoped transaction edits; partner OAuth requires separate production approval.
transactions.cleared webhook
Cards and funds: transaction webhooks ↗
transactions.cleared webhook · Checked 2026-10-16
Limit visibility -
-
Ramp Developer API / customer client credentials for transactions and scoped transaction edits; partner OAuth requires separate production approval.
Quickstart does not establish route throughput quotas
Developer API Quickstart ↗
Quickstart does not establish route throughput quotas · Checked 2026-10-16
CDC and deletion capture -
-
Ramp Developer API / customer client credentials for transactions and scoped transaction edits; partner OAuth requires separate production approval.
Cleared-transaction events do not establish all update/deletion identities
Cards and funds: transaction webhooks ↗
Cleared-transaction events do not establish all update/deletion identities · Checked 2026-10-16
Replay and gap recovery 2.5/10
Rebuild from a fresh snapshot; no historical replay established
Ramp Developer API / customer client credentials for transactions and scoped transaction edits; partner OAuth requires separate production approval.
Repeat transaction enumeration and follow page.next to rebuild the selected current transaction scope. Default results exclude declined transactions unless the declared state selection changes; historical versions, deleted payloads and durable event replay are not established.
Ramp transaction API reference ↗
List transactions, GET /developer/v1/transactions; data array and page.next; default excludes declined transactions · Checked 2026-10-16
Data exit
20% of the overall score before applicability adjustment.
Scored answers and evidence
Export custody 7.5/10
Customer-held structured files or API records
Ramp Developer API / customer client credentials for transactions and scoped transaction edits; partner OAuth requires separate production approval.
Customer-held structured API records within the declared resource scope
Ramp transaction API reference ↗
Customer-held structured API records within the declared resource scope · Checked 2026-10-16
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
Ramp Developer API / customer client credentials for transactions and scoped transaction edits; partner OAuth requires separate production approval.
Applicable post-cancellation retrieval clause not established by reviewed technical documentation
Developer API Quickstart ↗
Applicable post-cancellation retrieval clause not established by reviewed technical documentation · Checked 2026-10-16
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
Ramp Developer API / customer client credentials for transactions and scoped transaction edits; partner OAuth requires separate production approval.
Structured resource records can be retrieved; complete attachments, versions, relationships and native configuration remain unverified
Ramp transaction API reference ↗
Structured resource records can be retrieved; complete attachments, versions, relationships and native configuration remain unverified · Checked 2026-10-16
Business logic and customization
5% of the overall score before applicability adjustment.
Scored answers and evidence
Logic authoring 2.5/10
External integration code; native business logic portability not established
Ramp Developer API / customer client credentials for transactions and scoped transaction edits; partner OAuth requires separate production approval.
Customer integration code can run outside the provider; native workflow authoring not established
Developer API Quickstart ↗
Customer integration code can run outside the provider; native workflow authoring not established · Checked 2026-10-16
Rights to custom logic -
-
Ramp Developer API / customer client credentials for transactions and scoped transaction edits; partner OAuth requires separate production approval.
Ownership and reusable export or independent execution of native workflow artifacts remain unresolved
Developer API Quickstart ↗
Ownership and reusable export or independent execution of native workflow artifacts remain unresolved · Checked 2026-10-16
Scores are out of 10. * Incomplete evidence discounts verified capabilities (unknown answers stay unknown). Planned migration drives data exit. Scoring method ↗
CUSTOMER CHOICE
Third-party accessibility
Administrators create developer apps and choose scopes. Client credentials are for the customer application; the partner production route uses approved OAuth, and sensitive card-vault scopes have additional review.
Confirm who can connect, who owns the credentials and which uses are permitted. Customer consent and provider approval can be separate requirements; the selected plan and contract still matter.
READ / INTEGRATE
API and export routes
Transaction GET responses provide structured spend data. The public docs distinguish cards, bills and receipts rather than promising one complete accounting export; API pagination and selected scopes determine what is returned.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Ramp scoped API access | OAuth 2.0 | Integration provider | Yes | Partner approval | 2026-10-16 |
| Ramp customer-owned application | OAuth client credentials | Customer | No | Customer-supplied credentials | 2026-10-16 |
Availability depends on your product, plan and agreement. See the documentation below for the requirements of each route.
ECONOMIC ACCESS
Cost, authentication and limits
Minimum-plan API entitlement, fixed access fees and partner commercial terms remain unresolved. Product pricing and a developer token do not establish the fee structure for the whole assessed route.
Check API entitlement, credential ownership and rate limits for the route you intend to use. Include review fees, customer-plan upgrades and ongoing access charges in the total.
ACT FROM OUTSIDE
External action
Ramp documents a beta PATCH transaction endpoint for accounting selections, memos and line-item splits. This is a specific editing capability, not permission to move money or create payments.
Validate the supported operation, acting identity and permission scope (read access does not imply write permission). Ambiguous retries and revoked credentials also affect whether an external workflow can run safely.
KEEP ACCESS USEFUL
Continuity
Transaction webhooks can signal cleared spend. Neither undocumented timestamp filters observed by connector vendors nor receipt creation timestamps establish complete update/deletion capture across Ramp resources. Repeat transaction enumeration and follow page.next to rebuild the selected current transaction scope. Default results exclude declined transactions unless the declared state selection changes; historical versions, deleted payloads and durable event replay are not established.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | -Ramp Developer API / customer client credentials for transactions and scoped transaction edits; partner OAuth requires separate production approval. Cleared-transaction events do not establish all update/deletion identities | Cards and funds: transaction webhooks ↗Cleared-transaction events do not establish all update/deletion identitiesChecked 2026-10-16 |
| How can extraction recover after missed events or an interrupted consumer? | Rebuild from a fresh snapshot; no historical replay establishedRamp Developer API / customer client credentials for transactions and scoped transaction edits; partner OAuth requires separate production approval. Repeat transaction enumeration and follow page.next to rebuild the selected current transaction scope. Default results exclude declined transactions unless the declared state selection changes; historical versions, deleted payloads and durable event replay are not established. | Ramp transaction API reference ↗List transactions, GET /developer/v1/transactions; data array and page.next; default excludes declined transactionsChecked 2026-10-16 |
Useful ongoing access includes corrections and deletions, not only the first export. A failed request, changed filter or lost resource permission should not be interpreted as a deleted record.
LEAVE WITH YOUR DATA
Data exit and portability
A customer can retain permitted transaction records. Receipt binaries, later edits, card lifecycle states and native approval configuration require separate recovery checks; cancellation retrieval rights remain unresolved.
Test the output against the destination’s required fields and history. Check stable identifiers, relationships, attachments and extraction time; a sample file proves only the coverage of that sample.
BUILD / INSPECT / REUSE
Business logic and customization
Customer applications can apply external rules through scoped endpoints. Native approval configuration ownership and independent execution rights remain unresolved (transaction metadata is not a portable spend-policy runtime).
Custom API access, ownership of workflows and the right to export their definitions are separate questions. A custom-app capability alone does not establish that business rules can move to another system.
AGREEMENTS / API DOCS / PROGRAM REQUIREMENTS
Documented conditions
Answers below come from public provider materials. Every answer retains its source check date, scope (a partner agreement does not describe every customer route). Customer contracts and live behavior still need verification.
| Question | Answer / applicable route | Evidence |
|---|---|---|
| What structured read interface is documented? | Structured API for the declared product scopeRamp Developer API / customer client credentials for transactions and scoped transaction edits; partner OAuth requires separate production approval. Structured read interface for the declared product and resources | Ramp transaction API reference ↗Structured read interface for the declared product and resourcesChecked 2026-10-16 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsRamp Developer API / customer client credentials for transactions and scoped transaction edits; partner OAuth requires separate production approval. List transactions; GET /developer/v1/transactions and paginated data collection | Ramp transaction API reference ↗List transactions; GET /developer/v1/transactions and paginated data collectionChecked 2026-10-16 |
| What queries can a customer issue outside the provider UI? | Fixed object or report retrievalRamp Developer API / customer client credentials for transactions and scoped transaction edits; partner OAuth requires separate production approval. List transactions and transaction lookup; exact filter parameter coverage not scored | Ramp transaction API reference ↗List transactions and transaction lookup; exact filter parameter coverage not scoredChecked 2026-10-16 |
| Who decides whether a chosen third party may connect? | Separate provider consent or partner agreement requiredRamp Developer API / customer client credentials for transactions and scoped transaction edits; partner OAuth requires separate production approval. Partner integration; Ramp approves application before production customer OAuth | Ramp Developer API overview ↗Partner integration; Ramp approves application before production customer OAuthChecked 2026-10-16 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -Ramp Developer API / customer client credentials for transactions and scoped transaction edits; partner OAuth requires separate production approval. Reviewed entitlement documentation; minimum eligible plan and fixed route-specific access charges remain unresolved | Developer API Quickstart ↗Reviewed entitlement documentation; minimum eligible plan and fixed route-specific access charges remain unresolvedChecked 2026-10-16 |
| What permission is needed for the documented downstream use? | -Ramp Developer API / customer client credentials for transactions and scoped transaction edits; partner OAuth requires separate production approval. Reviewed access documentation; applicable downstream processing, AI and redistribution terms not established | Developer API Quickstart ↗Reviewed access documentation; applicable downstream processing, AI and redistribution terms not establishedChecked 2026-10-16 |
| Which external write operations are documented? | Named operations in a limited domainRamp Developer API / customer client credentials for transactions and scoped transaction edits; partner OAuth requires separate production approval. Transaction update beta; PATCH /developer/v1/transactions/{transaction_id} | Developer API changelog: transaction update beta ↗Transaction update beta; PATCH /developer/v1/transactions/{transaction_id}Checked 2026-10-16 |
| How can customers connect an application they build or choose? | Approved third-party applications using fixed interfacesRamp Developer API / customer client credentials for transactions and scoped transaction edits; partner OAuth requires separate production approval. Approved applications use the documented fixed API interfaces | Ramp Developer API overview ↗Approved applications use the documented fixed API interfacesChecked 2026-10-16 |
| What mechanism supports repeatable extraction of changes? | Documented updated-since filters or webhooksRamp Developer API / customer client credentials for transactions and scoped transaction edits; partner OAuth requires separate production approval. transactions.cleared webhook | Cards and funds: transaction webhooks ↗transactions.cleared webhookChecked 2026-10-16 |
| How are integration limits disclosed? | -Ramp Developer API / customer client credentials for transactions and scoped transaction edits; partner OAuth requires separate production approval. Quickstart does not establish route throughput quotas | Developer API Quickstart ↗Quickstart does not establish route throughput quotasChecked 2026-10-16 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsRamp Developer API / customer client credentials for transactions and scoped transaction edits; partner OAuth requires separate production approval. Customer-held structured API records within the declared resource scope | Ramp transaction API reference ↗Customer-held structured API records within the declared resource scopeChecked 2026-10-16 |
| What retrieval rights are documented at cancellation? | -Ramp Developer API / customer client credentials for transactions and scoped transaction edits; partner OAuth requires separate production approval. Applicable post-cancellation retrieval clause not established by reviewed technical documentation | Developer API Quickstart ↗Applicable post-cancellation retrieval clause not established by reviewed technical documentationChecked 2026-10-16 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedRamp Developer API / customer client credentials for transactions and scoped transaction edits; partner OAuth requires separate production approval. Customer integration code can run outside the provider; native workflow authoring not established | Developer API Quickstart ↗Customer integration code can run outside the provider; native workflow authoring not establishedChecked 2026-10-16 |
| What rights or portability are documented for custom workflow artifacts? | -Ramp Developer API / customer client credentials for transactions and scoped transaction edits; partner OAuth requires separate production approval. Ownership and reusable export or independent execution of native workflow artifacts remain unresolved | Developer API Quickstart ↗Ownership and reusable export or independent execution of native workflow artifacts remain unresolvedChecked 2026-10-16 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedRamp Developer API / customer client credentials for transactions and scoped transaction edits; partner OAuth requires separate production approval. Structured resource records can be retrieved; complete attachments, versions, relationships and native configuration remain unverified | Ramp transaction API reference ↗Structured resource records can be retrieved; complete attachments, versions, relationships and native configuration remain unverifiedChecked 2026-10-16 |
SOURCES / SCOPE / HISTORY
Sources and open questions
This review is based on the documentation below. Live account behavior and customer-specific agreements haven’t been tested.
Still to confirm
- Lowest eligible plan and fixed API access fees
- Applicable downstream-use and customer cancellation terms
- Complete file, history and configuration recovery
- Native workflow artifact ownership and independent execution
- Complete declared update and deletion identity coverage
- Retained replay, checkpoints and gap-recovery procedure
Documentation
Assessment checked 2026-10-16. Each answer retains its source and applicable route; the check date does not establish live account behavior.