Skip to content

Developer documentation

Use developer documentation when configuration is not enough and the installation needs code, integrations, C# business logic, or API automation.

Choose the path that matches the thing you are building. In the API, user documentation’s record types and records appear as entity definitions and entity instances; use the terminology bridge when moving between the two documentation tracks.

  1. Connect to a workspace API.
  2. Follow the Integration quickstart.
  3. Use the Runtime API reference for exact request and response contracts.
  1. Follow the Configuration quickstart.
  2. Use the Configuration API reference.
  3. For autonomous development, continue with the AI agent development quickstart.

Start with Business logic to choose between declarative behavior and trusted C# in the Net Operation Project. Then use the .NET SDK guide and .NET reference for the supported programming model.

Use the Workspace UI Project for the project structure, Moltaro and external API clients, design system, build and activation lifecycle, and observability.

The generated Runtime API and Configuration API references contain the published HTTP contracts. Read the versioned release notes before updating a long-lived integration or generated C# project. Coding agents can use llms-manifest.json to detect the exact published documentation revision.