# AppDirect integrations: companies and memberships

> Create a company, create a company membership and create a subscription in AppDirect, and start a workflow when AppDirect sends “User created”.

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

## Overview

AppDirect is a subscription commerce platform for running a marketplace that sells software and services, covering product catalogs, customer accounts, subscriptions and billing. Tray.ai connects to AppDirect through the HTTP Connector, so your workflows can call the AppDirect API alongside the rest of your stack.

## Use cases

### Users

Read, create, update, and delete users in AppDirect from any Tray.ai workflow. The AppDirect API covers calls such as create a user and read user details.

- Create a user
- Read user details
- Update a user

### Companies

Read, create, and update companies in AppDirect from any Tray.ai workflow. The AppDirect API covers calls such as create a company and read companies.

- Create a company
- Read companies
- Update a company

### Memberships

Create, update, and delete memberships in AppDirect from any Tray.ai workflow. The AppDirect API covers calls such as create a company membership and update a membership.

- Create a company membership
- Update a membership
- Delete a membership

### Subscriptions

Create, update, and delete subscriptions in AppDirect from any Tray.ai workflow. The AppDirect API covers calls such as create a subscription and change a subscription.

- Create a subscription
- Change a subscription
- Cancel a subscription

### AppDirect events

Start a Tray.ai workflow the moment something happens in AppDirect. AppDirect sends events such as user created and product modified to a Tray.ai webhook trigger.

- User created
- Product modified
- Subscription cancelled

## Challenges Tray.ai solves

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

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

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

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

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