Swedish newspapers 1871-1906

Open data API in a single place

Provided by Göteborgs universitet

Get early access to Swedish newspapers 1871-1906 API!

Let us know and we will figure it out for you.

Dataset information

Country of origin
Updated
2022.05.03 00:00
Created
2024.01.01
Available languages
English
Keywords
OCR, reference text, corpus, Language Technology (Computational Linguistics), fraktur, historical newspapers
Quality scoring

Dataset description

Svenska tidningar 1871–1906 contains a selection of digitized versions of Swedish newspapers from 1871 to 1906. It is part of the so called Kubhist corpus which was digitized at Kungliga biblioteket (KB). One newspaper was randomly selected from each year. For each newspaper two pages were selected, the second and fourth. All pages were automatically processed using advanced document layout analysis where each segment in the digitized page was framed and numbered. Each segment was processed with Abbyy FineReader version 11 and was manually transcribed by a transcription company who specializes in double-keying. This particular subset contains 74 pages, 45,445 segments and 337,635 words in total. It was produced as a part of the project Evaluation and refinement of an enhanced OCR-process for mass digitisation financed by RJ (dnr IN18-0940:1) for the period of 2019-2020.
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
countries and EU institutions
2019
API-first since
Free API quota
for evaluation and prototypes
SLA
history and push on production APIs
FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.
Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.
Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.
Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.
Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

European data discovery with free evaluation access and production-grade API options.

Copyright © 2026. Made by Apitalks