canonical: https://jentic.com/apis/tuemilio.com/tuemilio

# Tuemilio API

Tuemilio provides a waitlist management API for managing email subscribers, waitlists, referral tracking, and points-based engagement. The API exposes 8 endpoints secured with apiKey authentication.

## For AI agents

Programmatically create an email, get all emails. Covers 8 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for analytics only.

## Capabilities

- Create an email
- Get all emails
- Update an email
- Delete an email
- Add points to an email

## Use cases

### Analytics Operations

Use the Tuemilio API to perform analytics operations programmatically. The API provides 8 endpoints covering core functionality including create an email, get all emails, get an email by id.

Example prompt: Call POST `/lists/{list_id}/emails` to create an email

### Automated Emails Management

Automate emails operations by combining multiple Tuemilio API endpoints. Agents can get all emails and then get an email by id in a single workflow.

Example prompt: Call GET `/lists/{list_id}/emails` to get all emails, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Tuemilio API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'create an email', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/lists/{list_id}/emails` | Create an email |
| GET | `/lists/{list_id}/emails` | Get all emails |
| GET | `/lists/{list_id}/emails/{email_id}` | Get an email by ID |
| PUT | `/lists/{list_id}/emails/{email_id}` | Update an email |
| DELETE | `/lists/{list_id}/emails/{email_id}` | Delete an email |
| PUT | `/lists/{list_id}/emails/{email_id}/add-points` | Add points to an email |
| GET | `/lists` | Get all waitlists |
| GET | `/lists/{list_id}` | Get a waitlist |

## Key resources

- **Emails** — Operations related to Emails
- **Waitlists** — Operations related to Waitlists

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 49 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 87 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 51 / 100
  - Agent Usability: 94 / 100
  - Security: 15 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/tuemilio.com/tuemilio/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring Tuemilio API by hand means passing its api_token as a query parameter on every call, tracking list and email ids across calls, and handling errors and retries yourself. Through Jentic you install once, import Tuemilio API from the API Directory, store the API token once, and your agent calls it.
- **Permission scoping:** Tuemilio API puts the list id in the URL path (`/lists/{list_id}/emails/...`), so a rule can pin your agent to one list: it can add and read that list's emails and nothing else. You choose the operations it may call, so deleting an email is not included unless you add it.
- **Credential handling:** Your Tuemilio API token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'add an email to a list' or 'add points to a subscriber', and Jentic returns the matching Tuemilio API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Mixpanel** — Alternative analytics API
- **Amplitude** — Alternative analytics API
- **Segment** — Complementary analytics API
- **Pendo** — Complementary analytics API

## FAQ

### What authentication does the Tuemilio API use?

The Tuemilio API uses an API key passed in the `api_token` query. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I create an email with the Tuemilio API?

Yes. Use the POST `/lists/{list_id}/emails` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Tuemilio API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I create an email through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create an email'. Jentic returns the matching Tuemilio API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Tuemilio API have?

The Tuemilio API exposes 8 endpoints covering emails, waitlists operations.

### Can I limit what my agent is allowed to do with the Tuemilio API?

Yes. Because you run Jentic One yourself, your own rules decide which Tuemilio operations and credentials the agent may use. Since Tuemilio puts the list id in the URL path (`/lists/{list_id}/emails/...`), you can pin the agent to a single waitlist so it only adds and reads that list's emails. You also choose the operations it may call, so deleting an email stays off unless you explicitly include it.