We improve the publishing and naming of our documentation

The Positive credit register has been in operation for around 2.5 years, and one of the development challenges we have detected is how we release documentation for IT developers. In future, we will make efforts to pay more attention to clarity and uniformity when we name and release documentation. 

Up until now, especially the release of new and updated changes on the Upcoming changes page of the Documentation section on our website may have caused confusion. When we have updated documents, we have added the date of the update after the document, but the name of the document has remained unchanged.

How to interpret the documentation of upcoming changes

On the Upcoming changes page, we publish technical documentation in advance when we are planning to change the operation of our APIs in some way. In principle, we try to release multiple upcoming changes in one go, but sometimes it may be necessary to make new additions or changes to documents that have already been published. When updating a document in future, we will also change the name of the document and the way it is shown on the website. Further, we will state only the most recent date of publication for each document. For example, if it were necessary to update the description of the API for reporting data on loan contracts – available on the Upcoming changes page – before it is published on the Production documentation page, the document would be named as follows:

• Reporting data on loan contracts – API description (pdf) version 2.2. Document published on 1 April 2026.
• Reporting data on loan contracts – API description (pdf) version 2.2.rev1. Document published on dd mm yyyy.
• Reporting data on loan contracts – API description (pdf) version 2.2.rev2. Document published on dd mm yyyy.
• and so on.

In future we will also make sure that the version number is included in the document’s web address. The above changes apply to documents published on the Upcoming changes page after 1 September 2026. 

Production documentation remains unchanged

The new practices have no effect on the production documentation published on the Production documentation page. The version numbering of production documentation remains unchanged.