Developers overview

Use this section when integrating with Kuration from your own systems: REST workflow API (projects and rows) and webhooks (tool output events).

Prerequisites

• API access — The workflow API requires an account with API access. If your plan does not include it, the app shows API Access Locked under Settings → Integrations → API; upgrade or contact your Kuration admin as needed.
• API key — Create or rotate your key in the app. All enterprise API requests send the key in the kur-api-key header.
• Webhook URL (optional) — For event delivery, configure an HTTPS URL and store the webhook secret securely. See Webhooks.

Where to work in the product

Goal	In-app location
Generate or copy API key, see quick examples	/settings/integration?tab=api
Configure event webhook URL & secret; payload docs	/settings/integration?tab=webhooks

Docs in this site

• Workflow API — Base URL, authentication, and endpoint reference (aligned with the app and the enterprise_v3 router in the platform backend).
• Webhooks — tool_output_ready payload, X-Kuration-Signature verification, and Slack notifications.

If you change public HTTP behavior in the backend, keep these pages in sync (see AGENTS.md in kuration-docs).