REST API v1
Programmatic access to threads, messages and sending.
The REST API v1 gives programmatic access to threads and their messages. Base URL: https://app.astreo.de/api/v1.
Authentication
Every request carries a personal access token in the header:
curl https://app.astreo.de/api/v1/threads \
-H "Authorization: Bearer astreo_pat_xxxxxxxx"
Threads
List threads (with filters like unread) and fetch a single one:
GET /api/v1/threads
GET /api/v1/threads?unread=1
GET /api/v1/threads/{id}
The response includes subject, sender, timestamp, status and assignment, among others; the single fetch returns the history.
Messages
A conversation's messages are part of the thread detail (GET /api/v1/threads/{id}). A thread's internal
notes are available separately:
GET /api/v1/threads/{id}/notes
Sending
AI/agent workflows in Astreo follow the draft principle: suggestions are produced as an editable draft, the final send stays a deliberate action. For agentic flows (propose a draft) the MCP server is the intended path; event-based automation runs via webhooks.
Errors & rate limits
- 401 — token missing/invalid. 403 — token scope insufficient. 404 — resource not in your view.
- Errors come as JSON with
statusCodeandmessage. - The API is rate-limited; for bulk reads, plan for backoff on
429.