# Peaka integrations: projects and connections

> Create a project, create a connection and create a query in Peaka. Connect Peaka to the rest of your data and analytics stack with Tray.ai.

**Canonical page:** https://tray.ai/connectors/peaka-integrations/
**Categories:** Data and analytics
**Connects through:** HTTP Connector

## Overview

Peaka is a data platform that connects databases and SaaS apps into one queryable layer, with SQL queries, caching, exports and an AI agent over the data. Tray.ai connects to Peaka through the HTTP Connector, so your workflows can call the Peaka API alongside the rest of your stack.

## Use cases

### Projects

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

- List projects
- Create a project
- Update a project

### Connections

Read, create, update, and delete connections in Peaka from any Tray.ai workflow. The Peaka API covers calls such as list connections and create a connection.

- List connections
- Create a connection
- Update a connection

### Queries

Read, create, update, and delete queries in Peaka from any Tray.ai workflow. The Peaka API covers calls such as list queries and create a query.

- List queries
- Create a query
- Execute a query

### Catalogs

Read, create, and delete catalogs in Peaka from any Tray.ai workflow. The Peaka API covers calls such as list catalogs and create a catalog.

- List catalogs
- Create a catalog
- List tables

### Cache

Read, create, and delete cache in Peaka from any Tray.ai workflow. The Peaka API covers calls such as create a cache and trigger a full refresh.

- Create a cache
- Trigger a full refresh
- Get cache status

### Exports

Read and delete exports in Peaka from any Tray.ai workflow. The Peaka API covers calls such as export a query and export a table.

- Export a query
- Export a table
- List exports

## Challenges Tray.ai solves

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

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

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

The Peaka API uses a bearer token. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Peaka connector?

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