Working with Support chat

Support chat is one inbox for conversations with your customers, from the help-site chat, your app, email and WhatsApp. The API reads it, so your tools can report on it or prepare answers.

How it fits together

Read the inbox

1. Find what needs a person. The person view holds open conversations handed over by the AI agent, or with a customer waiting and nobody on them.
   cURLJavaScriptPython

   curl -G "https://api.olamma.sh/v1/w/your-workspace/conversations" \
     -H "Authorization: Bearer $OLAMMA_KEY" \
     --data-urlencode 'view=person' \
     --data-urlencode 'limit=20'

   const response = await fetch(`https://api.olamma.sh/v1/w/your-workspace/conversations?${new URLSearchParams({"view":"person","limit":"20"})}`, {
     headers: {
       Authorization: `Bearer ${process.env.OLAMMA_KEY}`,
     },
   });
   const data = await response.json();
   if (!response.ok) throw new Error(`${data.error.code}: ${data.error.message}`);

   import os
   import requests
   
   response = requests.get(
       "https://api.olamma.sh/v1/w/your-workspace/conversations",
       headers={"Authorization": f"Bearer {os.environ['OLAMMA_KEY']}"},
       params={"view":"person","limit":"20"},
       timeout=30,
   )
   data = response.json()
   response.raise_for_status()

2. Read one. You get the contact, the newest messages with team-only notes, any drafted reply, linked tasks and the customer’s other conversations.
   cURLJavaScriptPython

   curl "https://api.olamma.sh/v1/w/your-workspace/conversations/{id}" \
     -H "Authorization: Bearer $OLAMMA_KEY"

   const response = await fetch(`https://api.olamma.sh/v1/w/your-workspace/conversations/{id}`, {
     headers: {
       Authorization: `Bearer ${process.env.OLAMMA_KEY}`,
     },
   });
   const data = await response.json();
   if (!response.ok) throw new Error(`${data.error.code}: ${data.error.message}`);

   import os
   import requests
   
   response = requests.get(
       "https://api.olamma.sh/v1/w/your-workspace/conversations/{id}",
       headers={"Authorization": f"Bearer {os.environ['OLAMMA_KEY']}"},
       timeout=30,
   )
   data = response.json()
   response.raise_for_status()

3. Need older messages? When earlier is true, ask again with before set to the at of the first message you have.
   cURLJavaScriptPython

   curl -G "https://api.olamma.sh/v1/w/your-workspace/conversations/{id}" \
     -H "Authorization: Bearer $OLAMMA_KEY" \
     --data-urlencode 'before=2026-12-01T09:30:00.000Z'

   const response = await fetch(`https://api.olamma.sh/v1/w/your-workspace/conversations/{id}?${new URLSearchParams({"before":"2026-12-01T09:30:00.000Z"})}`, {
     headers: {
       Authorization: `Bearer ${process.env.OLAMMA_KEY}`,
     },
   });
   const data = await response.json();
   if (!response.ok) throw new Error(`${data.error.code}: ${data.error.message}`);

   import os
   import requests
   
   response = requests.get(
       "https://api.olamma.sh/v1/w/your-workspace/conversations/{id}",
       headers={"Authorization": f"Bearer {os.environ['OLAMMA_KEY']}"},
       params={"before":"2026-12-01T09:30:00.000Z"},
       timeout=30,
   )
   data = response.json()
   response.raise_for_status()

Search with query to look through every conversation, however old; a search ignores view.

curl -G "https://api.olamma.sh/v1/w/your-workspace/conversations" \
  -H "Authorization: Bearer $OLAMMA_KEY" \
  --data-urlencode 'query=refund' \
  --data-urlencode 'limit=10'

const response = await fetch(`https://api.olamma.sh/v1/w/your-workspace/conversations?${new URLSearchParams({"query":"refund","limit":"10"})}`, {
  headers: {
    Authorization: `Bearer ${process.env.OLAMMA_KEY}`,
  },
});
const data = await response.json();
if (!response.ok) throw new Error(`${data.error.code}: ${data.error.message}`);

import os
import requests

response = requests.get(
    "https://api.olamma.sh/v1/w/your-workspace/conversations",
    headers={"Authorization": f"Bearer {os.environ['OLAMMA_KEY']}"},
    params={"query":"refund","limit":"10"},
    timeout=30,
)
data = response.json()
response.raise_for_status()

Customers’ details are masked

Emails and phone numbers come back masked, like p***@acme.test, unless the key’s owner may see personal details. Linked tasks your key can’t read show only their id.

Replying isn’t in the API yet

A reply reaches a customer and can’t be taken back, so the API only reads for now. Notes, status changes and replies will come as their own step, with a person approving anything a customer would see.