Which service do you need?
Erbessd exposes condition monitoring data through several services. They are not variations of one API — they differ in where they run, how they authenticate and what they can give you.
EI-Analytic™ API
Section titled “EI-Analytic™ API”The cloud platform. If your machines already report into EI-Analytic™ and you want that data in your own system, this is the one.
- Hosted by Erbessd at
api.eianalytic.com - Gives you the company → area → machine → point → axis hierarchy, the devices, and their measurements including spectra and waveforms
- Authenticates with a session token per database
PHANTOM® Web Service
Section titled “PHANTOM® Web Service”A service you install on your own Windows Server. Your gateway posts raw sensor data to it and it stores each message as a JSON file you can read back. Choose this when the data must stay on your own infrastructure.
- Runs on your hardware, under IIS
- Gives you the raw sensor messages, closer to the wire than EI-Analytic™
- Requires you to install and maintain it
PHANTOM® Gateway protocols
Section titled “PHANTOM® Gateway protocols”The gateway speaks industrial protocols directly. No HTTP involved — use these when you are integrating with a SCADA, historian or PLC rather than writing application code.
- Modbus TCP — the gateway acts as a Modbus server on port 502
- MQTT — the gateway publishes to your broker
- OPC UA — the gateway acts as an OPC UA server on port 4334
A .NET client library, if you would rather not call the endpoints yourself.
→ SDKs
Choosing between them
Section titled “Choosing between them”| If you want to… | Use |
|---|---|
| Read processed data from the cloud | EI-Analytic™ API |
| Keep all data on your own network | PHANTOM® Web Service |
| Feed a SCADA, historian or PLC | Gateway protocols |
| Get raw waveforms closest to the sensor | PHANTOM® Web Service |
| Get spectra already computed | EI-Analytic™ API (GetFFT_Base64) |
Before you write client code
Section titled “Before you write client code”Each service documents its own conventions — request shape, response envelope, error reporting, dates and units. They are not the same, so read the one for the service you are integrating with rather than assuming:
The two HTTP APIs happen to share a response envelope, because both are built on the same .NET stack. That is a shared implementation detail, not a guarantee — their error codes already differ, and the gateway shares neither.