Table of Contents

Building Apps Overview

This section describes how applications integrate with ERP.net at a platform level.

Any software that connects to an ERP.net instance through its public APIs is treated by the platform as an ERP.net App. Apps are external to the core ERP and interact with it through well-defined boundaries.

What an ERP.net App Is

In ERP.net, an app is not a specific product or framework.
It is a role assigned to any application that communicates with an instance through APIs.

Apps may be implemented as:

  • User-facing applications
  • Background or service-based integrations
  • Automation or synchronization components
  • Reporting and analytics solutions

Apps can operate internally, connect external systems, or be distributed through the ERP.net Marketplace.

Different app designs are formalized as application types, which are described in more detail in Application Types.

Where Apps Run

Each ERP.net database is an instance.

Apps always connect to a specific instance and are subject to that instance's configuration, data scope, and access rules.

For details, see ERP.net Instances.

How Apps Are Identified and Controlled

Apps do not access an instance implicitly.

Each app is explicitly registered inside the instance and represented as a Trusted Application. This registration defines how the app is identified and what level of access it is granted.

Authentication and authorization are enforced by the ERP.net Identity Service and apply uniformly across all APIs.

Authentication, authorization, and related concepts are covered in detail in Authentication and Authorization.

How Apps Interact with the Platform

ERP.net exposes APIs that apps use to interact with data and functionality within an instance.

Different APIs are designed for different integration scenarios, such as application development or high-volume data access. The available API surface and access model depend on the app's design and intended use.

Guidance on selecting the appropriate API is provided in Choosing the right API.

High-Level Interaction Model

flowchart LR
  user([User or Service]) --- app([ERP.net App])

  subgraph "ERP.net Instance"
    direction TB
    idp([ERP.net Identity Service])
    api([ERP.net APIs])
    data([ERP.net Data])
    api --> data
  end

  app -->|Authenticate| idp
  app -->|API Calls| api

This model applies to all ERP.net Apps, regardless of implementation or deployment style.

How to Proceed

If you are ready to build an app, continue with Getting Started.

That section walks through the initial setup, app registration, and making your first API calls.

Suggest improvement to this page