# Acquire integrations: cases, messages and contacts

> Create a case, send a message and add a contact in Acquire, and start a workflow when Acquire sends “Chat set to active”.

**Canonical page:** https://tray.ai/connectors/acquire-integrations/
**Categories:** Customer service
**Connects through:** HTTP Connector

## Overview

Acquire is a customer service platform for live chat and messaging, where teams handle conversations and cases and keep records of contacts and companies. Tray.ai connects to Acquire through the HTTP Connector, so your workflows can call the Acquire API alongside the rest of your stack.

## Use cases

### Cases

Read, create, and update cases in Acquire from any Tray.ai workflow. The Acquire API covers calls such as list cases and get a case.

- List cases
- Get a case
- Create a case

### Messages

Read, create, update, and delete messages in Acquire from any Tray.ai workflow. The Acquire API covers calls such as list messages and send a message.

- List messages
- Send a message
- Update a message

### Contacts

Read, create, update, and delete contacts in Acquire from any Tray.ai workflow. The Acquire API covers calls such as list contacts and add a contact.

- List contacts
- Add a contact
- Update a contact

### Companies

Read, create, update, and delete companies in Acquire from any Tray.ai workflow. The Acquire API covers calls such as list companies and add a company.

- List companies
- Add a company
- Update a company

### Acquire events

Start a Tray.ai workflow the moment something happens in Acquire. Acquire sends events such as chat set to active and chat closed to a Tray.ai webhook trigger.

- Chat set to active
- Chat closed
- New case

## Challenges Tray.ai solves

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

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

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

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

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