01
A second sender
The transmission rules allow exactly one path between two market partners. An assistant with its own certificate is a new sender. The counterparty does not have to process what it did not agree to receive.
For the desk that tracks Redispatch, and does not send it
An energy market message the assistant may read, and may not send.
An energy market message for Redispatch 2.0 goes through RAIDA. Connect+ has offered it since 28 June 2021. The transports are email, SFTP and REST. SOPTIM builds the data provider. ION Allegro is a separate trading system with no public operation list on the product page. Reading a status is not sending a nomination.
Before any tool
An energy market message is a legal send
Redispatch 2.0 process data is not a chat attachment. The receiver is allowed to ignore a file that did not come from the agreed address.
- RAIDA, from Connect+, has been open to market participants since 28 June 2021.
- The transports named for it are email, SFTP and REST. Connect+ prefers REST.
- The RAIDA agent, built by SOPTIM, speaks REST and, since February 2026, email. SFTP is a different client.
- One agreed path between two market partners. A second sender is not a convenience. It is a message the other side need not process.
Checked 8 October 2026
Which energy market message question is a read
| Question | Where it lives | Agent |
|---|---|---|
| Did this redispatch document arrive? | RAIDA, on the agreed transport | Read the status the user already sees |
| Which transport is ours? | The pair already agreed: email, SFTP or REST | Name it. Do not open a second one |
| What is the nomination in the trading book? | ION Allegro, or Endur, if that is the desk | Read. Do not send the schedule |
| What is the AS4 state in billing? | Schleupen AS4 connect, a different door | Status at most. No answer sent |
| Sign and send the XML | The market role | No tool |
Allegro is not RAIDA, and Endur is not a small Stadtwerk default
RAIDA moves process data for congestion management between grid operators and the parties responsible for plant dispatch. Allegro is an ION system for utilities that trade power, gas and related commodities. ION describes connections to price providers, exchanges, pipelines, system operators and trade repositories. The product page does not publish the operations.
Gelsenwasser runs Allegro, with a loader for imports and exports that was later extended from gas to power. That is a trading integration. It is not a template for an assistant to nominate. Endur is the other ION trading system. No Endur API reference was opened for this page, so no Endur path is claimed.
Three ways to cause a market incident
Why an energy market message stays a status
02
A helpful send
The RAIDA agent exists so a participant can exchange files correctly, including signing and encryption. Using that capability from a model is still a send. The status question does not need it.
03
The wrong book
A schedule in Allegro and a redispatch document in RAIDA answer different duties. An agent that treats them as one queue will nominate when the user asked for a status, or the other way around.
Policy, not a call against RAIDA or a trading system.
allow: read_message_status | read_nomination_status
deny: sign | encrypt | send | nominate | open_second_transport
as: the user who already has the portal, on the transport already agreedSOPTIM builds RAIDA for Connect+. That does not make a SOPTIM energy-data login a market send.
Leave these where they are
An energy market message the blueprint will not automate
- Creating the XML. The RAIDA agent can convert from a sheet. A person still owns the file.
- Uploading a certificate. The portal at raida.de is an administrator step.
- Answering Schleupen AS4 market communication. Status at most, and only on the terms of the billing page.
- A public Endur operation. None was read, so none is listed.
When the portal is the whole job
If someone already lives in the RAIDA portal, they do not need a second window on the same status. Build the read when that status is being copied into a trading sheet or a control-room note. The signed list sits on the utility source system page. SOPTIM as energy data, which is not this send, is the SOPTIM connector.
From the message to the system that keeps it
- Utility source system — the read we will sign, and the send we will not
- Schleupen — AS4 status, not an answer
- SOPTIM — energy data, not the RAIDA send
What the market desk will ask
What may an agent ask about an energy market message?
Whether the message is present, and what status the portal already shows to that user. Composing, signing, encrypting or sending the XML is a send. It is not a question.
Which path should the connector use to RAIDA?
The path the two market partners already agreed. Connect+ names email, SFTP and REST, and prefers REST. The RAIDA agent covers REST and, since February 2026, email. A second path from an assistant is a different sender, and the receiver does not have to process it.
Is Allegro the same desk as RAIDA?
No. RAIDA moves redispatch process data between grid operators and plant operators. Allegro is an ION trading and risk system for utilities that trade power and gas. A nomination inside Allegro is a trade. A RAIDA document is a grid message. Neither is a tool that sends.
What does it cost to check one energy market message flow?
A two-week Readiness Blueprint at €4,900 net. We name the platform, the agreed transport and the status question, and we stop if the only credential can send. A production read is usually a pilot from €15,000.
Next step
Name the status the team already checks by hand
Two weeks. We look at the transport you already agreed, and we stop if the credential can send.