Prerequisites

These prerequisites apply before Oeconomia API can be used by an external ERP, accounting, or integration system.

Access Scope

Access must be approved for the relevant customer, Partner, equipment, and data scope. Oeconomia API uses one unified technical API, and the selected plan controls access level and commercial scope.

• Oeconomia API - Basic
• Oeconomia API - Premium
• Oeconomia API - Enterprise

Custom API forks or customer-specific API versions require separate formal approval and are not part of the standard Oeconomia API setup.

Login Credentials

Before the API can be used, Vikingegaarden A/S must create the required login credentials:

• Username
• Password
• Port or customer code

Network Access

API access is limited to approved and registered WAN IP addresses.

• The API can only be accessed from locations where the WAN IP address is approved and registered by Vikingegaarden A/S.
• The developer documentation can only be accessed from approved source locations.

Endpoint And Developer Documentation

The API DNS address is:

• ws1.vikingegaarden.com

After approval, developer documentation is available at https://ws1.vikingegaarden.com:8084/ppo/erp/doc-v1/redoc.html.

Security

• Communication between the client and API endpoint is encrypted with SSL/TLS.
• Access is limited to approved and registered IP addresses.
• Access is additionally limited by geo-blocking.

Before Integration

Before implementation, confirm the equipment identifiers, customer mapping, period handling, and expected data status workflow with Vikingegaarden A/S and the external system owner.

Shared Emiko Reference

For the generic Emiko model behind products, modules, service scope, and growth, see Products, Modules And Growth and Access, Permissions And Control.