Developers / Platform API
One API.
Self-hosted or hosted, the same.
Every Apteva instance exposes a REST API. Anything the dashboard can do, your code can do — create agents, install apps, move files, trigger deployments, read activity.
A request looks like this
curl https://your-instance/api/agents \
-H "Authorization: Bearer $APTEVA_API_KEY"What you can do
One key, one base URL
Authenticate with a bearer token against your own instance. Self-hosted and Cloud expose the same surface, so what you build against a laptop works unchanged in production.
Operate the platform
Agents, projects, app installs, files, tables, deployments and activity are all reachable. Anything the dashboard can do has an endpoint behind it.
Call any app's tools
Installed apps are reachable through the MCP gateway at a stable, name-keyed path. Your code calls the same tools an agent would, with the same permissions and the same audit trail.
Wire it into your own systems
Drive it from CI, a cron job, a webhook handler, or a service you already run. Agents become something you can start, steer, and observe programmatically.
A note on stability
This is the same API the dashboard uses, and it moves with the platform. Endpoint shapes can change between releases — pin a version when that matters to you, and check the documentation for the current reference.