Edgaze REST API
Run marketplace workflows from your backend. Same billing and execution as the product UI. Ship your first API call in minutes.
Base URL
Pin this origin in your SDK or HTTP client. All paths below are relative to it.
https://api.edgaze.ai/v1
How it works
Three primitives. Most integrations only need these.
Integration flow
From API key to completed run: the path most teams ship.
- 01Authenticate
Authorization: Bearer …
- 02Discover
GET /workflows
- 03Execute
POST /runs → 202
- 04Track
Poll or webhook
- 05Consume
Read outputs
Reference
Guides for auth, billing, and webhooks. Endpoint pages include a playground and copy-paste snippets.
Getting started
Workflows
- GETList Workflows
Discover current free and pay-per-run workflows in the paginated marketplace catalog.
- GETGet Workflow
Retrieve a single workflow with its input schema, access state, pricing, and an example run request.
- GETList Workflow Versions
List immutable workflow versions visible to the caller and inspect active and purchase pins.
- POSTAccept Workflow Update
Re-pin a buyer's purchase to the workflow's current active immutable version.
Runs
- POSTCreate Run
Start an asynchronous workflow run. Returns 202 Accepted with URLs to poll status and read events.
- GETList Runs
Page through your account's run history, newest first.
- GETGet Run
Poll canonical run status, failure reason, buyer-facing charge, and final outputs.
- POSTCancel Run
Stop a run that is still in flight. Cancelled runs are never charged.
- GETList Run Events
Read the durable event log for a run: started, node progress, and completion markers.
Guides
- Webhooks
Receive signed HTTP callbacks when runs reach terminal states. Manage endpoints from the Developer console.
- Errors & Edge Cases
Complete reference for error codes, HTTP status mapping, async failure modes, and security behavior.
- Billing & Spend Caps
How API runs are funded, capped, and charged relative to the product UI.
- Streaming & Real-time
Poll runs, read events, and stream live output during execution.
- OpenAPI specification
Machine-readable OpenAPI 3.1 document, generated from the same Zod schemas the handlers use.
Platform status
Live operational summary for API, runtime, and marketplace surfaces. Opens the public status page for incident history and component detail.
Developer console
Create keys, set spend caps, configure webhooks, and debug delivery.
Was this useful?
Your response helps us improve the documentation.