For the complete documentation index, see llms.txt. This page is also available as Markdown.

Overview

An overview of the VARIO Cloud dev documentation and its structure.

This section contains the technical documentation for extending and integrating VARIO Cloud — a cloud ERP system you can extend in three ways:

Approach
You build
Runs
Start here

REST API

An integration in any language that reads and writes ERP data over HTTP

Anywhere

Apps

A self-hosted web app embedded into the ERP UI, talking to the REST API

Your own infrastructure

Scripting

Server-side JavaScript running inside the ERP itself

VARIO backend

Most integrations combine them: an App for the UI and configuration, the REST API for data, Scripting for in-ERP automation, and Webhooks to react to changes.

While you build, the VARIO Cloud MCP server lets an AI assistant such as Claude Code, Cursor or VS Code explore the live API, query fields and VQL of your tenant — see AI Assistants (MCP).

Find your way

I want to call the API. Get a token via Authentication, then send requests to your tenant base URL — see REST API Introduction. Mind the rate limits, and query data with VQL.

I want to build an App. Read the Apps Introduction, then Create an App to get credentials, and follow the Quickstart. The App Manifest reference describes every field.

I want to react to changes in the ERP. Register a webhook — see Webhooks Introduction.

I want to automate business logic inside the ERP. No external server needed: use Workflows or Batch Processing, with the service layer and reusable Script Modules.

I want to store my own data on ERP records. Use Custom Fields to extend articles, accounts, documents and more.

I'm building a shop, shipping, banking, accounting or POS integration. These verticals follow established platform patterns. See App Backends for a one-page guide per domain.

I want my AI coding assistant to know VARIO Cloud. Connect it to your tenant through the MCP server — see AI Assistants (MCP).

Something isn't working as expected. Check the FAQ — it collects the mistakes developers hit most often.

How this documentation is organised

Section
Content

Base URL, authentication, rate limiting

Reacting to ERP events, registration, delivery

App model, credentials, manifest, quickstart

Concepts that apply everywhere: custom fields, VQL

Server-side JavaScript in the ERP

Connecting AI assistants to VARIO Cloud

FAQ

Common pitfalls and their answers

Beyond this space you'll also find the API Reference (every endpoint) and the Scripting Reference (every service and type).

New to the platform? Start with the Introduction of the section you need. Looking for a specific detail? Jump straight to the relevant page — every page is written to stand on its own.

Last updated

Was this helpful?