Skip to main content

Documentation Index

Fetch the complete documentation index at: https://parabola.io/docs/llms.txt

Use this file to discover all available pages before exploring further.

Ramp is a finance automation platform that combines corporate cards, expense management, bill payments, accounts payable, and procurement into a single system. Used by over 50,000 businesses, Ramp gives finance and ops teams real-time visibility into company spending, automates invoice processing, and syncs with accounting systems like NetSuite and QuickBooks. Connecting Ramp to Parabola lets ops teams automate AP workflows, reconcile bills against purchase orders, monitor payment statuses, and build custom spend reports without manual CSV exports or spreadsheet work.

​
Pull from Ramp

The Pull from Ramp step brings bills, purchase orders, transfers, and receipts directly into a flow. Use it to automatically retrieve bill and purchase order data for reconciliation and reporting, monitor payment status and approval workflows across vendors and entities, combine Ramp financial data with ERP, warehouse, and sales channel information, and build automated dashboards showing spend by vendor, status, and time period.

​
How to authenticate

Ramp uses OAuth 2.0 Client Credentials. To connect, you’ll base64 encode your Client ID and Client Secret and paste the result into Parabola. For a full walkthrough including a video, see Ramp’s Getting Started guide.

​
Creating API credentials in Ramp

1
Log in to Ramp as an Admin or Business Owner and navigate to Settings > Developer.
2
Click Create New App and give it a descriptive name (for example, “Parabola Integration”). Accept the Terms and click Create.
3
Under Grant types, click Add new grant type and select Client Credentials.
4
Under Scopes, click Configure allowed scopes and enable the scopes your integration needs:
  • bills:read — access bills and draft bills
  • transfers:read — access transfers
  • receipts:read — access receipts
  • purchase_orders:read — access purchase orders
5
Copy your Client ID and Client Secret. Store them securely, you’ll need them to connect in Parabola.
The scopes you select when connecting in Parabola must also be enabled in your Ramp app’s scope settings. If a scope isn’t permitted in Ramp, the connection will fail for that data type. Make sure both sides match.
Only users with Admin or Business Owner roles can create apps and generate API credentials in Ramp.

​
Connecting in Parabola

1
In your Parabola flow, add a Pull from Ramp step.
2
Base64 encode your credentials in the format client_id:client_secret and copy the result.
3
Click Authorize and enter your credentials in the form:
  • Authentication: paste your base64-encoded credentials. The value should look like Basic dXNlcjpwYXNz...
  • Scope: the scopes you want to use (for example, bills:read transfers:read purchase_orders:read receipts:read), separated by spaces. These must match scopes enabled in your Ramp app.
4
Click Connect. Parabola will securely store your credentials and handle token generation and renewal.

​
Available data

Using the Pull from Ramp step, you can access a range of financial and procurement data:
  • Bills: invoice and bill records including vendor details, amounts, invoice numbers, payment status (open, paid), approval status, due dates, issue dates, payment timestamps, line items with descriptions and amounts, accounting field assignments, sync status, and associated purchase order IDs. Filter by date ranges, payment status, approval status, sync status, vendor, amount range, and business entity.
  • Bill details by ID: full details for a specific bill using its unique identifier, including all line items, inventory line items, payment information, and vendor memos.
  • Draft bills: bills still in draft stage before submission, including vendor information, invoice numbers, line items, and creation timestamps. Filter by business entity, invoice number, or external system ID.
  • Draft bill details by ID: complete details for a specific draft bill using its unique identifier.
  • Transfers: payment transfer records including amounts, statuses (initiated, processing, completed, canceled, error), bank account associations, business entity, payment IDs, creation timestamps, and accounting sync status. Filter by transfer status, sync status, business entity, date ranges, and statement ID.
  • Transfer details by ID: full details for a specific transfer using its unique identifier.
  • Receipts: receipt records tied to transactions, including receipt image URLs, associated transaction IDs, uploading user, and creation timestamps. Filter by creation date, transaction date, specific transaction or reimbursement.
  • Receipt details by ID: a specific receipt record by its unique identifier, including a pre-signed download URL for the receipt image.
  • Purchase orders: PO records with PO numbers, vendor information, line items with quantities and unit prices, billing status (open, partially billed, fully billed, closed), receipt status (not received, partially received, fully received), associated bill and transaction IDs, spend dates, three-way match settings, and creation source. Filter by creation date, receipt status, creation source, business entity, spend request, and whether to include archived POs.
  • Purchase order details by ID: complete details for a specific purchase order, including all line items, associated bill IDs, item receipt IDs, and spend program information.

​
Common use cases

  • Three-way match reconciliation: Pull purchase orders and bills from Ramp, combine with receiving data from your ERP or warehouse, and flag discrepancies in quantities, pricing, or missing documents. Push the cleaned output into NetSuite or QuickBooks Online.
  • AP aging and payment monitoring: Track open bills by due date and vendor to identify overdue invoices, monitor approval bottlenecks, and alert finance teams in Slack when payment deadlines approach.
  • Spend analysis and vendor reporting: Aggregate bill and PO data by vendor, business entity, or time period, then push the result to Google Drive, Smartsheet, or BI tools like Looker and Metabase.
  • Accounting sync reconciliation: Monitor sync status across bills, transfers, and POs to identify records that haven’t synced to NetSuite, QuickBooks Online, or Microsoft Dynamics Finance, so the books stay current.
  • Receipt compliance auditing: Pull receipts alongside transactions to flag missing receipts, late submissions, and policy exceptions across the organization.
  • Purchase order tracking and variance analysis: Monitor POs from creation through billing and receiving, flag POs with partial receipts or overbilling, and combine with shipment data from FedEx, UPS, or ShipStation for full procurement visibility.

​
Tips for using Parabola with Ramp

  • Match scopes on both sides. The scopes selected in Parabola must be enabled in your Ramp app. If a scope is missing in Ramp, the corresponding data type will fail to load.
  • Schedule around close. Daily or hourly runs during month-end close keep AP data current and reduce last-minute reconciliation work.
  • Filter by status and date. Pull “bills updated in the last 7 days” or “POs with status open” instead of pulling the entire history each run, which keeps flows fast.
  • Join Bills with Purchase Orders. Most three-way match flows need both endpoints joined on the associated PO ID. Use a Combine tables step on purchase_order_id.
  • Add validation rules. Use Filter and Formula steps to flag exceptions like bills without matching POs, POs stuck in “open” status for more than 60 days, or transfers in error status.
  • Document your flow. Ramp exposes many endpoints with overlapping fields. Step notes help the next person reading the flow understand the AP, procurement, and reconciliation logic.

​
FAQ

​
Can I push data back into Ramp?

The Pull from Ramp step is read-only. To create or update Ramp records (for example, marking a bill as approved), use a Send to an API step pointed at the relevant Ramp endpoint with your OAuth credentials.

​
Why is my connection failing for one data type but working for others?

Most often, the scope for that data type isn’t enabled in your Ramp app. Open Settings > Developer > Your App > Scopes in Ramp and confirm the scope is allowed, then reconnect in Parabola.

​
How do I pull receipt images?

The Receipts endpoint returns receipt metadata and a pre-signed image URL. To download the image, use a Pull from an API step against that URL, or pass the URL through to wherever you’re storing receipts (for example, Google Drive or Box).

​
Does the integration support Ramp’s Bill Pay and accounting sync data?

Yes. Bills, transfers, and POs all expose sync status and accounting field assignments. Use those fields to reconcile against NetSuite, QuickBooks Online, or whatever ERP Ramp is syncing to.
With Ramp and Parabola connected, the AP reconciliations, three-way matches, and spend reports that used to live in spreadsheets run on a schedule, with clean data flowing into the systems where finance and procurement actually work.
Last modified on May 18, 2026