# Typing & read receipts

> Show the real typing indicator and send real read receipts from your own automations.

## Show typing

POST https://beam.aisync.link/v1/typing · body: {"to": "+1555...", "action": "start" | "stop"}
curlCopy
```
curl -X POST https://beam.aisync.link/v1/typing \
  -H "x-api-key: YOUR_WORKSPACE_KEY" \
  -H "Content-Type: application/json" \
  -d '{"to": "+15551234567", "action": "start"}'
```

The lead sees live typing bubbles until you send stop or a message. The pattern that feels most human: typing on, wait a few seconds scaled to message length, send. (Beam's inbox and assistant already do this automatically; this endpoint is for your own automations.)

## Send a read receipt

POST https://beam.aisync.link/v1/read · body: {"to": "+1555..."}
curlResponseCopy
```
curl -X POST https://beam.aisync.link/v1/read \
  -H "x-api-key: YOUR_WORKSPACE_KEY" \
  -H "Content-Type: application/json" \
  -d '{"to": "+15551234567"}'
```

```
{ "status": "sent" }
```

The lead sees "Read" under their message. Read receipt plus typing plus a reply seconds later is exactly what a fast human looks like.
Blue bubble onlyBoth endpoints work on iMessage contacts with an existing conversation. Texting has no typing or read concepts, and Beam returns a clear error rather than pretending.