# Planyo integrations: reservations and resources

> Add a reservation payment, add a resource and create a voucher in Planyo. Connect Planyo to the rest of your operations stack with Tray.ai.

**Canonical page:** https://tray.ai/connectors/planyo-online-booking-integrations/
**Categories:** Operations
**Connects through:** HTTP Connector

## Overview

Planyo is an online reservation system for businesses that rent resources, such as rooms, equipment, and classes, with availability, pricing, and payment management. Tray.ai connects to Planyo through the HTTP Connector, so your workflows can call the Planyo API alongside the rest of your stack.

## Use cases

### Reservations

Read, create, update, delete, and manage reservations in Planyo from any Tray.ai workflow. The Planyo API covers calls such as make a reservation and list reservations.

- Make a reservation
- List reservations
- Modify a reservation

### Resources

Read, create, and update resources in Planyo from any Tray.ai workflow. The Planyo API covers calls such as list resources and add a resource.

- List resources
- Add a resource
- Modify a resource

### Users

Read, create, update, and delete users in Planyo from any Tray.ai workflow. The Planyo API covers calls such as add a user and list users.

- Add a user
- List users
- Modify a user

### Coupons and vouchers

Read and create coupons and vouchers in Planyo from any Tray.ai workflow. The Planyo API covers calls such as create a voucher and generate a coupon.

- Create a voucher
- Generate a coupon
- List coupons

### Invoices

Read and create invoices in Planyo from any Tray.ai workflow. The Planyo API covers calls such as generate an invoice and list invoices.

- Generate an invoice
- List invoices

### Webhooks

Create and delete webhooks in Planyo from any Tray.ai workflow. The Planyo API covers calls such as add a notification callback and remove a notification callback.

- Add a notification callback
- Remove a notification callback

## Challenges Tray.ai solves

### Keeping Planyo 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 Planyo 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 Planyo 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 Planyo 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 Planyo?

Yes. Tray.ai connects to Planyo through the HTTP Connector, which calls the Planyo API directly. Any call the Planyo API documents can run as a step in a Tray.ai workflow.

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

The Planyo API uses an API key in the query string. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Planyo connector?

Planyo runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Planyo connector from the Planyo 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/
