API and webhooks

Shard now plugs into your own systems. With the new API and webhooks, your code can start automations, read results, and react to events, in both directions.

Whether you're a platform engineer wiring Shard into a deploy pipeline or an ops lead connecting an internal tool, you no longer need to wait for a built-in integration.

What's new

• API keys: create keys with exactly the permissions they need, like starting runs or reading run history, and revoke them any time.

• Start runs from code: trigger an automation with a single API call and pass in the data it needs.

• Read results: fetch the status, steps, and output of any run.

• Webhook trigger: every automation can have its own unique URL. Send an event to it and the automation starts.

• Send webhooks: add a Send webhook action to push data to any endpoint, signed so you can verify where it came from.

• Smart retries: if your endpoint is down, Shard retries with increasing delays.

Built to be safe

Keys are shown once, scoped by permission, and recorded in the audit log. Every webhook Shard sends carries a signature you can check before trusting the payload.

Where to find it

Create a key under Settings → API keys. The documentation covers authentication, starting runs, and webhooks, with examples to copy.