# Rydoo integrations: expenses and receipts

> Add an expense, upload a receipt and add a project in Rydoo, and start a workflow when Rydoo sends “Expense submitted”.

**Canonical page:** https://tray.ai/connectors/rydoo-integrations/
**Categories:** Finance
**Connects through:** HTTP Connector

## Overview

Rydoo is an expense management platform where employees submit receipts and expenses, managers approve them, and finance teams export them to accounting or ERP systems. Tray.ai connects to Rydoo through the HTTP Connector, so your workflows can call the Rydoo API alongside the rest of your stack. API access comes through Rydoo's partner program or API plan, so you need approved credentials first.

## Use cases

### Expenses

Read and create expenses in Rydoo from any Tray.ai workflow. The Rydoo API covers calls such as add an expense and get an expense.

- Add an expense
- Get an expense
- Reject expenses

### Receipts

Read and create receipts in Rydoo from any Tray.ai workflow. The Rydoo API covers calls such as upload a receipt and download a signed receipt.

- Upload a receipt
- Download a signed receipt

### Users

Read, create, and update users in Rydoo from any Tray.ai workflow. The Rydoo API covers calls such as add a user and search for users.

- Add a user
- Search for users
- Get a user

### Groups

Read, create, and update groups in Rydoo from any Tray.ai workflow. The Rydoo API covers calls such as list groups and add a group.

- List groups
- Add a group
- Get a group

### Projects

Read, create, and update projects in Rydoo from any Tray.ai workflow. The Rydoo API covers calls such as list projects and add a project.

- List projects
- Add a project
- Get a project

### Transactions

Read and create transactions in Rydoo from any Tray.ai workflow. The Rydoo API covers calls such as add a transaction and list transactions.

- Add a transaction
- List transactions

## Challenges Tray.ai solves

### Keeping Rydoo credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Rydoo credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Rydoo API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Rydoo API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Rydoo?

Yes. Tray.ai connects to Rydoo through the HTTP Connector, which calls the Rydoo API directly. Any call the Rydoo API documents can run as a step in a Tray.ai workflow. API access comes through Rydoo's partner program or API plan, so you need approved credentials first.

### How does Tray.ai authenticate with Rydoo?

The Rydoo API uses OAuth 2.0. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Rydoo connector?

Rydoo runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Rydoo connector from the Rydoo API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/