# Amilia integrations: programs and activities

> Start a Tray.ai workflow when Amilia sends “Program created”. Connect Amilia to the rest of your operations stack with Tray.ai.

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

## Overview

Amilia is registration and management software for recreation, sports and community organisations, handling programs, activities, memberships, bookings and payments. Tray.ai connects to Amilia through the HTTP Connector, so your workflows can call the Amilia API alongside the rest of your stack.

## Use cases

### Programs

Read programs in Amilia from any Tray.ai workflow. The Amilia API covers calls such as get programs and get a program.

- Get programs
- Get a program
- Get a program's activities

### Activities

Read activities in Amilia from any Tray.ai workflow. The Amilia API covers calls such as get all activities and get an activity.

- Get all activities
- Get an activity
- Get persons in an activity

### Persons

Read persons in Amilia from any Tray.ai workflow. The Amilia API covers calls such as get persons and get a person.

- Get persons
- Get a person
- Get a person's registrations

### Memberships

Read memberships in Amilia from any Tray.ai workflow. The Amilia API covers calls such as get memberships and get a membership.

- Get memberships
- Get a membership
- Get sold memberships

### Registrations

Read registrations in Amilia from any Tray.ai workflow. The Amilia API covers calls such as get registrations and get a registration by webhook ID.

- Get registrations
- Get a registration by webhook ID

### Webhooks

Read, create, and delete webhooks in Amilia from any Tray.ai workflow. The Amilia API covers calls such as get webhooks and create a webhook.

- Get webhooks
- Create a webhook
- Delete a webhook

## Challenges Tray.ai solves

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

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

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

The Amilia API uses basic authentication 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 Amilia connector?

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