Translation. Original: srodowiska.md
KSeF API 2.0 Environments
16.03.2026
Below is a summary of the public environments.
| Abbr. | Environment | Description | API Documentation | Allowed Formats |
|---|---|---|---|---|
| TEST | Test (Release Candidate) | Environment for testing integration with KSeF API 2.0, contains RC versions. | https://api-test.ksef.mf.gov.pl/docs/v2 | FA(2), FA(3), FA_PEF (3), FA_KOR_PEF (3) |
| DEMO | Pre-production (Demo) | Environment matching the production configuration, intended for final integration validation under conditions close to production. | https://api-demo.ksef.mf.gov.pl/docs/v2 | FA(3), FA_PEF (3), FA_KOR_PEF (3) |
| PRD | Production | Environment for issuing and receiving invoices with full legal force, with guaranteed SLA and actual production data. | https://api.ksef.mf.gov.pl/docs/v2 | FA(3), FA_PEF (3), FA_KOR_PEF (3) |
<font color="red">Warning:</font> Test environments (TE/DEMO) are intended solely for testing integration with the KSeF API. Do not submit production invoices or real entity data to them.
In the test environment TE, authentication using self-signed certificates is permitted, which in practice means that many integrators can authenticate in the context of the same company. For this reason, data entered in the TE environment is not isolated and may be shared between integrators. Use random NIP identifiers for testing, avoiding any real data.
URL addresses returned by the API
In every case when the API returns a URL address for downloading or uploading a resource, its host corresponds to the environment to which the call was directed (TEST, DEMO or PRD).
Maintenance work on test environments
Due to the planned, systematic development of the National e-Invoice System (KSeF 2.0), from October 1, 2025, periodic maintenance work may be carried out on the System's test environments.
This work will take place between 4:00 PM and 6:00 PM. During this time, temporary difficulties accessing the test environments may occur.
After maintenance is completed, only changes affecting integration will be published in the changelog — for example, changes in API behavior, contract modifications, XSD schema changes, limits, etc. Changes that do not affect the API and are invisible from an integration perspective — such as internal quality, performance, or security fixes — may not be communicated or will be presented in summary form.