---
title: "Contact Tarkle (for AI agents)"
description: "How an AI agent files a support request with the Tarkle team for a user, reads the reply, or writes the email, and what an agent cannot do."
---

> Documentation Index
> Fetch the complete documentation index at: https://tarkle.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Contact Tarkle (for AI agents)

Use this page when a person asked an agent to get in touch with Tarkle, or when the help center and the API cannot answer what they need.

There are two ways: **the support API** (no account and no API key) and **email**. Prefer the API. It gives a request id, and you can read the team's answer with it. The team answers by email to the address in the request.

The same text is at [`https://tarkle.com/contact.md`](https://tarkle.com/contact.md).

## Try these first

1. Search the [help center](https://tarkle.com/help). Add `.md` to an article address for its Markdown, or read [`https://tarkle.com/help.md`](https://tarkle.com/help.md) for the index.
2. Plans, prices and limits: [`https://tarkle.com/pricing.md`](https://tarkle.com/pricing.md). Never quote a price from memory.
3. Is Tarkle down? [status.tarkle.com](https://status.tarkle.com).
4. Something to read or change in a workspace: the [API](/docs/api). It needs an API key the user creates in Tarkle under Settings, API. An agent cannot create one.

## File a support request with the API

`POST https://tarkle.com/api/support/requests` with a JSON body. No API key. The person's email address is where the team replies.

```bash
curl -X POST https://tarkle.com/api/support/requests \
  -H "Content-Type: application/json" \
  -d '{"email":"person@example.com","name":"Pat Lee","subject":"Upload stops at 90%","message":"What happened, what was expected, steps, time with time zone, error code, what was tried. Written by an AI agent for Pat Lee.","agent":"your agent name"}'
```

| Field | Rule |
| --- | --- |
| `email` | Required. The address the reply goes to. |
| `message` | Required. 10 to 5000 characters. Put in it what the email section below lists. |
| `subject` | Optional. Up to 120 characters. The first line of the message is used if you leave it out. |
| `name` | Optional. The person's name. |
| `agent` | Optional. The name of your agent, so the team sees what sent it. |

The answer is `201` with `id`, `ref`, `reply_to` and `access_token`. Keep the `access_token`. It is shown once, and it is the only way to read the thread or add to it.

- **Read the thread and the team's reply:** `GET https://tarkle.com/api/support/requests/{id}` with `Authorization: Bearer <access_token>`. The result has `status`, `has_team_reply` and `messages`. Each message has `from` (`you` or `tarkle_team`), `text` and `created_at`.
- **Add to the same request:** `POST https://tarkle.com/api/support/requests/{id}` with the same header and `{"message":"..."}`.
- **Errors:** `422` with `details` for each field, `429` when one address or email sends too many (a few every 10 minutes and every day), `404` for a wrong id or token, `502` or `503` when support is unavailable. Then use email.
- Replies are written by people. Check again after minutes, not seconds.

## Who to write to by email

| Question | Address |
| --- | --- |
| Support, billing, invoices, plans, custom storage, payment by invoice | support@tarkle.com |
| Legal notices, terms, appeals, security reports (subject "Security"), abuse reports (subject "Abuse report"), copyright notices (subject "DMCA notice") | legal@tarkle.com |
| Privacy requests: a copy of personal data, a correction or a deletion | privacy@tarkle.com |

## How to write the email

One problem per email or request. Include:

- **Subject:** one line that names the problem, for example "Upload stops at 90% in workspace abc12345".
- **Account email:** the address the user signs in with.
- **Workspace key:** the 8-character key from the workspace address, when the problem is in one workspace.
- **What happened and what was expected,** in plain sentences, in order.
- **Steps to repeat it, the time it happened (with time zone), the page address and any error message.** An API error has a `code` and a `request_id`; include both.
- **What you already tried.**
- **A line saying an AI agent wrote the email for the user,** and what the user asked for, so the team knows who to answer.

Never put these in an email, a chat or a file: a password, a sign-in code, an API key (it starts with `tk_`), a card number or the content of a private file. If the team needs one, they will say how to share it safely.

## Reports the team handles first

- A security hole: write to legal@tarkle.com with the subject "Security". Describe it. Do not run it against other people's data.
- Illegal content or misuse: legal@tarkle.com with the subject "Abuse report" and the page address.

## What an agent cannot do

- Create an account, an API key, an organization or a subscription for the user. A person does it in the app.
- Pay for a plan without the user. Give the user the checkout link from [`https://tarkle.com/api/pricing/products`](https://tarkle.com/api/pricing/products).
- Read the person's inbox. The reply reaches the person by email. The API only shows the thread you filed, with your `access_token`.
- Change or delete an account or its data without the owner. Privacy requests go to privacy@tarkle.com, and the team checks who is asking first.

Source: https://tarkle.com/docs/ai-agents/contact-tarkle/index.mdx