Skip to end of banner
Go to start of banner

myneva.daarwin - Externe API

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Current »

The API is not versioned.
It is possible that breaking changes will occur in the future.

Required Server version >= 7.0

The API is currently a restlike ASP.NET 4.7.2 Web API.

The request objects are complex objects and Http-GET does not support this, all routes are made available as Http-POST routes with body parameters.

Below is a complete description of the available routes, including the objects, in OpenApi 2.0 format.

BaseUrl Example https://rz.qmcenter.de/203405/ServerBase

Testable API-URI: https://rz.qmcenter.de/203405/ServerBase/api/getserverversion

Swagger documentaion https://rz.qmcenter.de/203405/ServerBase/swagger/docs/v1

Postman-Example:

 On-premise-Customers

BaseUrl can find in QMCenter.exe.config

<configuration>
<system.serviceModel>
<client>
<endpoint name="ServerBase_.." address = http://localhost/ServerBase/…” >

BaseUrl in that case is “http://localhost/ServerBase

Almost every Request needs LogingData to manage permission and licence checks.

Where can I find the required information for the LoginData

 LoginData

DBAlias, CustomerNo and ContractNo can be found in “QMCenter.exe.config”

That config file will be found in daarwin execution Path

image-20240104-115215.png

"DBAlias": QMCenter.exe.config/configuration/QMCServer/Key
"CustomerNo": QMCenter.exe.config/configuration/QMCServer/Value/KdNr
"ContractNo":QMCenter.exe.config/configuration/QMCServer/Value/203405

"Username": daarwin login username
"Password": daarwin login password

Request Header Content-Type must be application/json;

Api-Sections

myneva.daarwin - Externe API - Reporting

  • No labels