Blog: SaaS Factory Now Has a Public API — Integrate It Into Any Engineering Workflow

SaaS Factory Now Has a Public API — Integrate It Into Any Engineering Workflow

v1.0.118

From day one, SaaS Factory's mission has been clear: no human should be the bottleneck. But until now, every external integration with the platform required a human to open the dashboard and click a button. That's a bottleneck. We've fixed it.

With v1.0.118, SaaS Factory ships a public REST API and a webhook outbound system — the two primitives you need to slot the platform into any engineering workflow you already have.

The Problem We Solved

Every serious automation platform lives and dies by its API surface. Competitors like Devin and Factory.ai win enterprise deals not just because of what they can do autonomously, but because they plug directly into existing workflows via APIs, @mentions, Slack bots, and CI hooks. When a team's issue tracker, CI pipeline, and chat tools can all talk to the AI platform without anyone switching context, adoption becomes frictionless.

SaaS Factory had the autonomous agents. It had inbound webhooks for GitHub and Stripe. What it didn't have was an outward-facing API — a way for users to trigger pipelines, query the feature queue, push features from external tools, or receive real-time events about what the platform was doing. Every integration was manual. That's now changed.

What's Shipped

A REST API That Does What You'd Expect

Three core endpoints cover the most important integration surface:

POST /api/v1/features — Push a feature directly into the pipeline from any tool: a GitHub Action, a Linear webhook, a Slack slash command, a cron job. If it can make an HTTP request, it can now talk to SaaS Factory.
GET /api/v1/features — Query the feature queue by status. Pull this into your internal dashboard, your Retool app, your ops runbook. Live pipeline visibility, anywhere.
POST /api/v1/pipelines/trigger — Trigger a pipeline run on demand. Useful for event-driven automation — kick off a development cycle the moment a milestone is hit or a ticket is closed.

Authentication is via API keys scoped to your organization, generated from Settings.

Outbound Webhooks That Keep Your Tools in Sync

The REST API handles requests to SaaS Factory. The webhook system handles events from it.

Configure an HTTPS endpoint and subscribe to the events that matter to you:

feature.created / feature.started / feature.completed / feature.failed
pr.opened
ci.passed / ci.failed
release.shipped

When any of these happen, SaaS Factory POSTs a signed JSON payload to your endpoint within seconds. Every payload is HMAC-SHA256 signed so you can verify it came from the platform. Failed deliveries are retried with exponential backoff for up to 24 hours.

What You Can Build With This

Automated feature intake from GitHub Issues. Label an issue saas-factory and a GitHub Actions workflow pushes it straight into the pipeline. No copy-paste, no dashboard tab, no delay.

Slack notifications on release. Subscribe to release.shipped and post to your engineering channel automatically. Everyone knows what shipped without anyone having to check.

Live ops dashboards. Poll the feature queue API to display pipeline status on whatever internal tooling your team already uses.

Event-driven cross-tool workflows. Connect ci.failed to PagerDuty. Connect feature.completed to close a Linear ticket. The webhook system is generic — wire it to anything.

No Breaking Changes

Existing inbound webhooks — GitHub, Stripe, and support integrations — are unaffected. Dashboard access and existing sessions continue to work exactly as before. This release is purely additive.

Get Started

Go to Settings → API Access and generate an API key.
Make your first request: GET /api/v1/features to see your current feature queue.
Go to Settings → Webhooks, add an endpoint, and subscribe to release.shipped to see the webhook system in action.

Full API and webhook reference: Public REST API & Outbound Webhooks

The platform that says no human should be the bottleneck should never itself be one. With a public API and outbound webhooks, SaaS Factory now fits into any workflow — human-driven or fully automated.