# commercetools integrations

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

**Canonical page:** https://tray.ai/connectors/commercetools-integrations/
**Categories:** E-commerce
**Connects through:** HTTP Connector

## Overview

commercetools is a headless commerce platform that stores products, carts, orders, and customer accounts behind an API for online storefronts. Tray.ai connects to commercetools through the HTTP Connector, so your workflows can call the commercetools API alongside the rest of your stack.

## Use cases

### Products

Read, create, update, and delete products in commercetools from any Tray.ai workflow. The commercetools API covers calls such as query products and get a product.

- Query products
- Get a product
- Create a product

### Carts

Read, create, update, and delete carts in commercetools from any Tray.ai workflow. The commercetools API covers calls such as query carts and get a cart.

- Query carts
- Get a cart
- Create a cart

### Orders

Read, create, update, and delete orders in commercetools from any Tray.ai workflow. The commercetools API covers calls such as query orders and get an order.

- Query orders
- Get an order
- Create an order from a cart

### Customers

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

- Query customers
- Get a customer
- Create a customer

## Challenges Tray.ai solves

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

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

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

The commercetools API uses OAuth 2.0 and 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 commercetools connector?

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