Skip to content

Legacy endpoints ​

Two things carry the word legacy on this platform. Neither needs action from an existing integration.

Metagrapho ​

The endpoints previously documented as the Metagrapho API are the /v2/processes endpoints of the Transkribus API. Nothing about them has changed: paths, request and response bodies, status values and link rel values are identical, and existing integrations continue to work without any modification. If you built against the Metagrapho documentation, you are already using the Transkribus API; only the name and the documentation home are new.

Text recognition on stored documents ​

The Transkribus REST API, the server behind the app, used to offer text recognition on documents stored in a collection (/recognition/{collId}/{modelId}/trhtr and PyLaia decoding). Those calls are being retired. Recognition on the platform is the Transkribus API's single-image job: Recognise text. Everything else on that server stays: Collections, Documents with upload and export, Analyse documents, Models with training, and Search.

Transkribus Developer Platform