Developer documentation

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

Public documentation and workspace APIs use different URLs

https://moltaro.com/docs/ is the public documentation site. Every /api/workspace/... request in this section must be sent to the target installation’s workspace API base URL. Start with Connect to a workspace API before using a quickstart or copying an endpoint.

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.

Start here

Integrate with an existing application

1. Connect to a workspace API.
2. Follow the Integration quickstart.
3. Use the Runtime API reference for exact request and response contracts.

Configure an application through the API

1. Follow the Configuration quickstart.
2. Use the Configuration API reference.
3. For autonomous development, continue with the AI agent development quickstart.

Build C# business logic

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.

Build custom workspace pages

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

API client guides

• Reliable API automation — concurrency, idempotency, retry, recovery, safety, and audit rules.
• Asynchronous operations — determine the execution model and poll jobs, runs, schedules, actions, and builds.
• Errors and responses — response envelopes, validation failures, recoverable errors, and the installation’s machine-readable error catalog.
• Error code reference — the installed error catalog of Entity record mutations, plus other stable error and diagnostic identifiers.

Entity and record APIs

• Entity list page API — configure permanent Statement filters and preserve page scope in hosted queries and YAML.
• Object collaboration API — bounded history, direct anchors, quotes, deferred files, and idempotent composite Send.
• Entity search — configure search targets and use the Runtime API SearchTerm condition.
• Entity Instance Query — exact filtering, sorting, projection, and paging payloads.
• Composite Entity mutations — create and update records in one transaction as the caller, up to the host’s step limit (100 by default), over REST and C#.
• Form Related Table API — configure and automate embedded child-record tables.
• Record matching — configure exact and fuzzy duplicate detection and track complete scans.
• Record Merge — prepare and execute explicit pairwise merges with concurrency, idempotency, and Association set-union.

Module walkthroughs

• Boards configuration
• Boards items and moves
• Tasks configuration
• Tasks runtime automation
• Tasks asynchronous recipes
• Tasks deadline reporting
• Workflow configuration
• Workflow runtime API and C#
• Workflow process document and nodes
• Work Schedule
• Entitlement Operations
• Record history and audit

Reference and updates

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.