From 4b1e7b29558019a1e0f0685f517df570851ff242 Mon Sep 17 00:00:00 2001 From: sorabot <32125183+sorabot@users.noreply.github.com> Date: Fri, 21 Aug 2026 11:51:24 +0400 Subject: [PATCH] docs: mark the public test environment unavailable Both hostnames the page hands out stopped resolving when the environment was torn down, so a reader following it meets DNS failures with no explanation. Say so at the top and point at the production host until the environment returns. Signed-off-by: Dmitrii Creed --- src/getting-started/public-test-environment.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/src/getting-started/public-test-environment.md b/src/getting-started/public-test-environment.md index 42d1357..5291586 100644 --- a/src/getting-started/public-test-environment.md +++ b/src/getting-started/public-test-environment.md @@ -1,5 +1,11 @@ # Public test environment +::: warning NOTE + +The public test environment is currently unavailable and the hostnames below do not resolve. Until it is restored, integrate against the production host given in [Calling API endpoints](./calling-api-endpoints.md#base-url). + +::: + The test environment is a safe and controlled environment where you can try out and experiment with the FIB API without affecting the production system. Here, you can make mistakes, test different scenarios, and learn how to use the API. To access the test environment, you need to follow the same steps as for the production environment. The only difference is that you will be provided with test credentials instead of production credentials (see [Connection details](#connection-details) below).