REST API

Lobu exposes HTTP APIs so you can trigger agents and integrate with external systems.

Features

• Messaging endpoint to send messages to agents over api, slack, telegram, and internal platform routes.
• Bearer token authentication for API access control.
• Multipart file upload support with per-file and total-size limits.
• OpenAPI-documented routes for schema-driven integrations.
• Platform-aware routing fields (for example Slack channel/thread metadata).

Interactive API Reference

Browse all endpoints, try requests, and see response schemas in the full API reference.

The reference is auto-generated from the gateway’s OpenAPI spec and always reflects the latest routes.

Calling agents from TypeScript? Reach for the typed @lobu/client instead of hand-rolling HTTP: same endpoints, typed sessions and SSE streaming. To extend what an agent sees and does rather than call it over the wire, see Connectors and Reactions.

Quick Start

# Send a message to an agent
curl -X POST http://localhost:8787/lobu/api/v1/agents/{agentId}/messages \
  -H "Authorization: Bearer $LOBU_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "platform": "api",
    "content": "Hello!"
  }'

To route the message into a Slack workspace instead, set platform to slack and include a slack routing object:

curl -X POST http://localhost:8787/lobu/api/v1/agents/{agentId}/messages \
  -H "Authorization: Bearer $LOBU_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "platform": "slack",
    "slack": { "channel": "C0123456789", "thread": "1700000000.000100" },
    "content": "Hello!"
  }'

Typical Use Cases

• Connect backend workflows to an agent programmatically.
• Trigger agent tasks from webhooks, cron jobs, or internal services.
• Build custom UI clients on top of Lobu’s gateway API.