Skip to main content
The test environment lets you test your integration with the Engrate API before you go live. You use a test organization. Engrate connects the test organization to a simulated market. Nothing that the test organization sends reaches the real market. The simulated market sends the same kinds of message as the real market. It plays the Scheduling Area Responsible and your counterparties. Because of this, the API shows the same state, statuses and match reports as in production. How it is different from the real market gives the differences. The test environment is available for the Netherlands. There, the simulated market takes the place of the TenneT MMC Hub.

​
What the simulated market does

​
How it is different from the real market

  • Answers come in a few minutes or less. The real market answers over hours. The simulated market keeps the order of the answers, but it makes the time between them shorter.
  • Your counterparties follow a scenario. The scenario sets the values that your counterparties send and what goes wrong during the day. See Scenarios.
  • Allocations come from one run each day. The simulated market does not send later corrections.
  • The data is test data. The counterparties and the accounting points do not exist in the real market. Use only the identifiers that we give you.

​
Scenarios

A scenario is one delivery day from the first revision to the last confirmation report. Each delivery day that you send starts the scenario again. Your test organization has one scenario for domestic series and one for foreign series. If you do not ask for a scenario, you get a normal day. With the scenario, we send you a test package. The test package gives the EAN-13 codes of your counterparties, the schedule that you send at each step, and what the API returns after each step. Your counterparties send fixed values, so your series match only when you send the values from the test package. To change the scenario, contact us.

​
Get started

1

Ask for a test organization

Contact us. Tell us the scenario that you want and the size of the test portfolio for allocations. We make a test organization for you, separate from your production organization, and connect it to the simulated market. Then we send you the test package. For foreign series, it also gives the identifiers of the capacity contracts.
2

Get an API key

The test organization has its own sign-in to the Engrate Console. Your production sign-in cannot make API keys for the test organization. Sign in to the test organization and make an API key, as in Authentication. Keep it apart from the API key of your production organization. The API key selects the organization, and the organization selects the market that receives your schedules.
3

Send a schedule

Send a schedule with "market": "NL" and "tso": "TENNET_TSO", in the same way as in Send your first schedule. Use the receiver_id and the EAN-13 codes from the test package. For foreign series, set market_agreement_id to the capacity contracts from the test package. Use the same URL as in production, https://api.engrate.io.
4

Read the results

Read the revisions, the series state and the match reports with the same endpoints as in production. Compare the results with the test package.

​
Go live

To go live in the Netherlands, TenneT requires a qualification test in its own test environment. We can connect a test organization to that environment for you. When you pass the qualification test, we connect your production organization to TenneT. Then send your schedules with the API key of your production organization. Your test organization stays connected to the simulated market. You can continue to use it for tests.