# Acumatica integrations: sales orders

> Create a sales order and create a stock item in Acumatica. Connect Acumatica to the rest of your ERP stack with Tray.ai.

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

## Overview

Acumatica is a cloud ERP system covering financials, sales orders, inventory, purchasing and project accounting for mid-sized companies. Tray.ai connects to Acumatica through the HTTP Connector, so your workflows can call the Acumatica API alongside the rest of your stack.

## Use cases

### Sales orders

Read, create, and update sales orders in Acumatica from any Tray.ai workflow. The Acumatica API covers calls such as retrieve sales orders and create a sales order.

- Retrieve sales orders
- Create a sales order
- Update a sales order

### Stock items

Read, create, and update stock items in Acumatica from any Tray.ai workflow. The Acumatica API covers calls such as retrieve stock items and create a stock item.

- Retrieve stock items
- Create a stock item
- Update a stock item

### Bills and adjustments

Read bills and adjustments in Acumatica from any Tray.ai workflow. The Acumatica API covers calls such as retrieve bills and release a bill.

- Retrieve bills
- Release a bill

## Challenges Tray.ai solves

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

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

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

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

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