> For the complete documentation index, see [llms.txt](https://docs.kick.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kick.co/integrations/ramp.md).

# Ramp

Sync your Ramp credit card transactions, reimbursements, and bills directly into Kick.

Connecting Ramp gives you a live view of all your Ramp card transactions, employee reimbursements, and bills inside Kick - categorized and posted to your books automatically.

{% hint style="info" %}
You must be an **admin** of your Ramp account to connect the integration.
{% endhint %}

***

### Connect Ramp

**From the Accounts tab:**

1. Go to the **Accounts** tab
2. Click **Add account** and select **Ramp**
3. Authenticate with your Ramp admin credentials and follow the prompts

**From the Bill Pay tab:**

1. Go to the **Bill Pay** tab
2. Click **Connect Ramp**
3. Authenticate with your Ramp admin credentials

Both methods connect the full integration - card transactions, reimbursements, and bills all sync regardless of where you connect.

***

### What syncs

* **Credit card transactions** - all Ramp card spend, [categorized](/common-workflows/categorization.md) automatically
* **Reimbursements** - employee expense reimbursements processed through Ramp
* **Bills** - bills created in Ramp, visible in Kick's [Bill Pay](/common-workflows/bill-pay.md) tab with AP aging and vendor details

***

### Bills in Kick

Once Ramp is connected, your bills appear in the **Bill Pay** tab. You can view them by vendor, by bill, or by line item - and see which are upcoming, overdue, or paid.

→ [Bill Pay](/common-workflows/bill-pay.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.kick.co/integrations/ramp.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.