API
Integrate Semogram with HTTP requests, starting with a pipeline run
The Semogram HTTP API lets your service manage workspace resources, execute pipelines, read data and published queries, and participate in governed writes. Requests use ordinary HTTPS and JSON. An MCP client instead discovers tools and invokes them through the MCP protocol; tool names are not HTTP routes.
Your service → HTTPS + workspace API key → Semogram API
├─ Workspace resources
└─ Project → pipeline → runUse https://platform.semogram.com/api/v1 as the production base URL. The key determines the workspace; project routes also require a project UUID belonging to that workspace.
Start with a pipeline
Run your first pipeline request walks through selecting a saved pipeline, creating a scoped key, starting a run and retrieving its status. A successful execution request accepts work; it does not prove the destination has been updated.
Resources
| Resource | What your integration can do |
|---|---|
| Pipelines | Inspect, author, version, activate and execute pipelines |
| Runs | List and inspect execution results |
| Projects | Discover, create, rename and delete projects |
| Data endpoints | Configure targets, check access, discover schema and read records |
| Queries | Manage queries and releases; execute published reads |
| Ontology | Inspect compiled definitions and maintain read bindings |
| Access | Manage keys, grants and workspace consumer settings |
| Governed writes | Manage policies, source writes, actions and change delivery |
| Integrations | Submit observations and acknowledge corrections |
| Usage and billing | Inspect charges, alerts, plans and billing navigation |
Availability
The route catalog lists implemented HTTP methods. Plugin installation, forecasting authoring, workspace membership invitations, Company SSO setup and pipeline schedule/cancellation actions do not currently have corresponding public /api/v1 routes. Use their documented platform or MCP flows. Do not infer a REST route from an MCP tool name.
The API exposes several generations of response shapes. Each resource guide explains its envelope; callers must inspect HTTP status before treating a response as success.