Call It
Drive Ductor over REST, Connect-RPC, or the CLI — the most complete track in these docs.
Ductor is API-first and headless: everything the product does is reachable over one surface, served as both REST/JSON and Connect-RPC from the same Protocol Buffers definitions. This is the most complete track here.
API reference
The practical tour — auth model, tenancy, resource groups, and the interactive reference.
Guides
End-to-end walkthroughs: define a workflow, add a connector, route an event, issue a key.
Managing resources
Provision and operate tenants, pools, rules, workflows, experiments, and connections.
API surface
The transport contract — protocol planes, interceptors, versioning, pagination, rate limits.
Start with a working request
Issue & use API keys
Mint a tenant key, scope it with roles and environments, and authenticate with it.
Define & publish a workflow
Author a DAG in YAML, validate it offline, publish a version, then trigger it.
Routing rules & strategies
Create pools, write CEL rules, and pick a selection strategy.
Errors & status codes
Domain sentinels mapped to Connect/gRPC codes, HTTP status, and Problem JSON.
Neighbouring tracks
Authoring the same routes visually is Click it. Defining workflows in your own codebase instead of over the API is Extend it.