# Ramp Developer API Machine-readable index for Ramp's Developer API documentation. ## Usage Instructions - If you are given a docs URL on docs.ramp.com or any preview host such as *.ramp-api-docs.pages.dev, do not fetch the rendered HTML page for content. These pages are JavaScript shells. - If the URL or question points to a guide-style page under /developer-api/v1/ and not under /developer-api/v1/api/, fetch the matching file under /llms-guides/. Example: /developer-api/v1/rate-limiting -> /llms-guides/rate-limiting.txt. - If the URL or question points to an API reference page under /developer-api/v1/api/, read /llms-api.txt instead of the HTML page. - If you are not sure which guide matches, read /llms.txt for the guide index, then fetch the specific /llms-guides/.txt file. - If a guide references specific endpoints, use the guide file in /llms-guides/ for the workflow and /llms-api.txt for the schema details. ## Guides - [Accounting](/llms-guides/accounting.txt) - Ramp's API can be used to keep data in sync between Ramp and an external accounting system. - [ERP Migration Tool](/llms-guides/accounting-erp-migration.txt) - This guide explains how integrators can set up a new API-based accounting connection to use the ERP migration tool. - [Applications](/llms-guides/applications.txt) - The Applications API lets developers programmatically pre-fill Ramp applications on behalf of new businesses. Each application creates a new business in Ramp and kicks off an asynchronous approval process. - [Authorization](/llms-guides/authorization.txt) - Ramp uses OAuth 2.0 for secure API access, providing granular permission control through scopes and supporting multiple authorization flows for different use cases. - [Bill Pay](/llms-guides/bill-pay.txt) - A bill is the structured accounts payable record in Ramp—the object that powers approvals, coding, and payment. - [Build with Ramp](/llms-guides/build-with-ramp.txt) - Ramp enables technology partners to build integrations that reach 50,000+ businesses. This guide walks you through building, testing, and publicly listing on the Ramp Integrations page. - [Cards and Funds](/llms-guides/cards-and-funds.txt) - Ramp's Developer API gives you programmatic control over funds, cards, and spending policies to help your teams spend responsibly and track budgets in real time. Whether you're managing departmental budgets, team events, or office expenses, these APIs provide the building blocks for automated spend management. - [Changelog](/llms-guides/changelog.txt) - Stay up to date with our latest API updates via RSS feed (reader required). - [Ramp CLI](/llms-guides/cli.txt) - Authenticate with OAuth, manage expenses, approve bills, book travel, and more from your terminal or AI agent. - [Custom Records](/llms-guides/custom-records.txt) - The Custom Records API allows you to extend Ramp's data models with your own custom fields and data. Whether you need to add custom fields to existing Ramp objects or create entirely new data structures, this API provides the flexibility to integrate Ramp with your business processes. - [Data Relationships](/llms-guides/data-relationships.txt) - Relationship information is automatically shown in each resource's documentation. Look for relationship indicators next to UUID fields that reference other resources. - [Debugging](/llms-guides/debugging.txt) - Ramp APIs will return an x-trace-id header in all API responses. The x-trace-id is particularly helpful for debugging, as it enables correlation between logs, metrics, and the API response, providing greater visibility into how the request was processed. - [Deferred Tasks](/llms-guides/deferred-tasks.txt) - Some API calls, for example requesting for a new card, require asynchronous processing. They are all denoted with /deferred/ in the request URL. - [Developer MCP](/llms-guides/developer-mcp.txt) - The Developer MCP server is subject to change. Feedback and questions can be submitted via a Developer API support ticket. - [Errors](/llms-guides/error-handling.txt) - The Ramp API returns detailed error information in the response body along with standard HTTP status codes. This allows you to quickly diagnose and address issues with your API requests. - [Getting Started](/llms-guides/getting-started.txt) - This guide will help you make your first Ramp API call in just a few minutes. You'll create an access token and call the Transactions API to retrieve transaction data. - [Introduction](/llms-guides/introduction.txt) - Automate spend, connect your systems, and build powerful integrations—all with one API. - [MCP](/llms-guides/mcp.txt) - The Model Context Protocol (MCP) enables AI assistants to securely connect to your business data and systems. Instead of copying and pasting information or switching between applications, you can ask your AI assistant direct questions about your Ramp account and get instant, accurate answers. - [Monetary Values](/llms-guides/monetary-values.txt) - In the Ramp API, monetary values are represented by the currency_code and amount. All currency_code values are three-letter acronyms as defined in ISO 4217 (e.g., USD for US Dollars). There are two representations of the amount: - [Pagination](/llms-guides/pagination.txt) - Pagination allows you to retrieve an entire dataset with a series of requests, where each request fetches a portion of the data set. By loading data in smaller chunks, pagination reduces the amount of data transmitted per response and alleviates the load on the servers, ensuring faster loading times and a smoother user experience. - [Ramp MCP](/llms-guides/ramp-mcp.txt) - Ramp MCP is subject to change. Feedback and questions can be submitted via a Developer API support ticket. - [Rate Limiting and Timeouts](/llms-guides/rate-limiting.txt) - API requests that take longer than 60 seconds will be terminated and return a 504 Gateway Timeout response. Most API requests complete well within this limit, but if you're working with large datasets or complex queries: - [Sandbox](/llms-guides/sandbox.txt) - The Ramp sandbox is a testing environment where developers and partners can safely build, test, and experiment with Ramp's API without affecting live production data. - [Sync Button](/llms-guides/sync-button.txt) - This guide explains how integrators can set up the Accounting Sync Button for Accounting API-based connections. Once enabled for your integration, connected customers can initiate transaction and reimbursement syncs directly from the Ramp UI. - [Tax Codes](/llms-guides/tax-codes.txt) - Tax code endpoints are currently in Beta. During the beta, endpoints may be subject to breaking changes, which will be announced via the Changelog. - [Vendor Credits](/llms-guides/vendor-credits.txt) - This guide explains how integrators can enable and use vendor credits with the Ramp API. - [Virtual Cards](/llms-guides/virtual-cards.txt) - Due to PCI compliance requirements, 16-digit card numbers and CVVs are not available in production without approval. All customers will see these fields in Sandbox. Submit a Developer API support ticket to begin the qualification process for access. - [Embedded Cards](/llms-guides/virtual-cards-embedded.txt) - Ramp Embedded Cards allow you to securely display card numbers and CVV codes to users via an iframe. If you want to programmatically create cards for a virtual card issuing flow where partners can easily create virtual cards to pay travel, maintenance, and other third-party vendors on their own platforms, see our Virtual Cards guide. - [Webhooks](/llms-guides/webhooks.txt) - Webhooks allow your application to receive real-time notifications about events that occur in your Ramp account. Instead of polling our API, webhooks push notifications to your specified endpoint whenever an event happens. ## API Reference - [OpenAPI spec](/openapi/developer-api.json) - Canonical OpenAPI schema. - [Plain-text API reference](/llms-api.txt) - Generated endpoint and schema reference. ## Full Exports - [Plain-text guides index](/llms-guides.txt) - All guides in one file. - [Combined guides and API reference](/llms-full.txt) - Single file with both guides and endpoint reference.