Lithuania OSP Statistics Scraper

Lithuania OSP Statistics Scraper

Scrape official Lithuanian statistics by indicator code, with optional date range and language, up to a million data points per run. Every row returns the indicator value, period, and metadata exactly as published. No API key or registration needed. Export to CSV, JSON, Excel, or XML.

Lithuania's Official Statistics Portal publishes thousands of economic, demographic, and social indicators, but browsing and downloading them manually is slow. This Actor reads the public OSP API directly, so you feed it an indicator code and it returns every data point in one flat table. Filter by start and end period and choose English or Lithuanian labels.

Who uses it	What they scrape Lithuania OSP for
Economists	Pull long-run GDP, inflation, or employment series for a forecast model.
Policy analysts	Track demographic or social indicators across municipalities over time.
Data journalists	Gather official figures for a story on population change or trade.
Academic researchers	Build a panel dataset of regional statistics for a paper.

What it does

This Actor collects official statistical data points from the Lithuania OSP API by indicator code and returns each observation as a flat row.

• 📅 Date range filter: limit results to a start and end period with ISO-8601 values.
• 🌐 Language selection: request labels in English or Lithuanian (lt).
• 📊 Full indicator history: omit the date range to get every observation the OSP holds for that code.
• ⚙️ Direct API passthrough: the Actor calls the OSP SDMX API with the parameters you set, no intermediate scraping.

Results export to CSV, JSON, Excel, or XML, or straight from the API.

What you can do with Lithuania OSP data

📈 Build a macroeconomic dashboard.

An economist runs the Actor weekly for GDP, CPI, and unemployment indicators, appending the latest period to a live dashboard.

🗺️ Compare regional statistics.

A policy analyst pulls population and income indicators for all municipalities and joins them in a GIS tool to map disparities.

📰 Fact-check a news article.

A journalist enters the indicator code cited in a government press release to verify the exact figures and historical context.

🎓 Assemble a research dataset.

A PhD student collects decades of education or health statistics for a difference-in-differences study.

Why choose this scraper

	What you get
Official source	Data comes straight from the Lithuania OSP SDMX API, the same backend that powers the portal.
One call per indicator	Feed it a code like S3R629_M3010217 and get every matching observation in one run.
Flat, analysis-ready output	Each row is one observation with its period, value, and metadata, ready for Excel or a database.
No auth or API key	The public OSP API requires no registration, and neither does this Actor.

How it compares

No other Store actor targets Lithuania OSP the same way, so the honest comparison is with the alternatives teams actually weigh.

	Lithuania OSP Statistics Scraper	Build it in-house	By hand
Setup	Run it now, zero config	Days of engineering	None, but hours per pull
When Lithuania OSP changes	Maintained for you	You fix it	You re-learn the page
Proxies, retries, anti-bot	Built in	Your problem	Browser only
Output	Fixed JSON schema, CSV/Excel export	Whatever you build	Copy-paste
Cost	Pay per result	Engineering time	Analyst hours

Configure the run

Drive the Actor with an indicator code, and optionally narrow the results by start period, end period, and response language. The Input tab lists every parameter.

A first run with the defaults:

{
  "indicator": "S3R629_M3010217",
  "maxItems": 10
}

A larger pull:

{
  "indicator": "S3R629_M3010217",
  "maxItems": 200
}

Pricing

Pay-per-result: $0.0018 per result collected. You pay only for the results written to your dataset.

Results collected	Approximate cost
100 results	$0.18
1,000 results	$1.80
10,000 results	$18.00

New Apify accounts start with $5 in free credit.

Free users

Free-plan runs return up to 10 results as a preview. Upgrade your Apify plan to collect up to 1,000,000 results per run.

Run it

1. Create a free Apify account with $5 in credit.
2. Open the Lithuania OSP Statistics Scraper.
3. Set your inputs and any filters, then click Start.
4. Export the results as CSV, Excel, JSON, or XML from the Dataset tab.

Run it programmatically through the Apify API (run-sync-get-dataset-items) or the ApifyClient for JavaScript and Python.

Use with AI agents (MCP)

Give an AI agent live access to Lithuania OSP through the Model Context Protocol. Add the Actor to Claude, Cursor, or any MCP client:

$claude mcp add --transport http apify "https://mcp.apify.com?tools=parseforge/lithuania-osp-statistics-scraper"

Then prompt it in plain language to run the scraper and read back the results.

Troubleshooting

The run returns no data points.

Check that the indicator code is exactly correct. Try the code without a date range first to see if any observations exist, then add startPeriod and endPeriod.

I get an error about an invalid period format.

Use ISO-8601 format: 2020 for a year, 2020-01 for a month, or 2020-01-15 for a day. Do not write quarters like Q1.

The run times out.

Some indicators have millions of observations. Set a lower maxItems value or narrow the date range with startPeriod and endPeriod.

The labels are in the wrong language.

Set the lang field to en for English or lt for Lithuanian. The default is English.

I cannot find the indicator I need.

Visit the OSP data portal and use the search. Once you open a table, the indicator code is often visible in the page URL or the metadata panel.

FAQ

Question	Answer
Where do I find the indicator code?	Browse the Lithuania OSP data portal, open an indicator table, and look for the SDMX dataflow or indicator ID in the URL or metadata tab. It often looks like S3R629_M3010217.
Can I scrape multiple indicators in one run?	The Actor takes one indicator code per run. To collect several indicators, run the Actor once per code, or use an Apify workflow to chain multiple runs.
What format are the dates in?	The startPeriod and endPeriod fields accept ISO-8601 strings. For annual data use a year like 2020, for monthly use 2020-01, and for daily use 2020-01-15.
Does this Actor work with all OSP datasets?	It works with any dataset exposed through the public SDMX API. Most tables on the portal are available, but a few legacy tables may use a different backend.
Is there a rate limit?	The public OSP API does not enforce strict rate limits, but very large requests may time out. Use the maxItems setting to cap the result set if needed.
Can I get data in Lithuanian?	Yes, set the lang field to lt and all labels and metadata will be returned in Lithuanian.
What does the output look like?	Each row is one observation: a period, a numeric value, and dimension columns that describe what the value measures and where.
Do I need an API key for the OSP?	No, the Lithuania OSP public API is open. This Actor calls it directly with no authentication.
How do I export the results?	After the run finishes, download your dataset as CSV, JSON, Excel, or XML from the Apify storage tab.

Related actors

• eurostat-scraper: Use this instead when you need statistics published by Eurostat rather than the Lithuania national portal.

Browse the full ParseForge collection for more scrapers.

🆘 Need help? Email parseforge@protonmail.com with your run ID, your input, and what you expected.

⚠️ Disclaimer. This Actor is unofficial and is not affiliated with, endorsed by, or sponsored by Official Statistics Portal of Lithuania. It collects only publicly available data. You are responsible for using the collected data in compliance with the source's terms of service and applicable data-protection laws, including GDPR, CCPA, and PIPL. Do not use it to collect personal data unlawfully.