# Apparound integrations

> Call the Apparound API from any Tray.ai workflow with the HTTP Connector.

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

## Overview

Apparound is sales software for building product configurations, price quotes and contracts, with customer records and e-signature requests in one place. Tray.ai connects to Apparound through the HTTP Connector, so your workflows can call the Apparound API alongside the rest of your stack.

## Use cases

### Customers

Read, create, and update customers in Apparound from any Tray.ai workflow. The Apparound API covers calls such as list customers and get a customer.

- List customers
- Get a customer
- Create a customer

### Quotes

Create quotes in Apparound from any Tray.ai workflow. The Apparound API covers calls such as start a configuration session and create a cart.

- Start a configuration session
- Create a cart
- Add an item to a cart

### Contracts

Read and delete contracts in Apparound from any Tray.ai workflow. The Apparound API covers calls such as get a contract and get a contract by number.

- Get a contract
- Get a contract by number
- Generate a contract from a quote

### Attachments

Read and delete attachments in Apparound from any Tray.ai workflow. The Apparound API covers calls such as save an attachment and download an attachment.

- Save an attachment
- Download an attachment
- Delete an attachment

### Signatures

Create and delete signatures in Apparound from any Tray.ai workflow. The Apparound API covers calls such as send a signature request and remove a signature request.

- Send a signature request
- Remove a signature request

## Challenges Tray.ai solves

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

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

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

The Apparound 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 Apparound connector?

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