Platform · Spain and Italy

Spain and Italy Fuel Data

Two open regimes, two very different file habits, and one breaking change in 2026.

Spain publishes station-level prices through the ministry's hydrocarbon geoportal and a free REST service that needs no key, with stations legally obliged to report price changes. Italy publishes two daily CSV files — prices as at 08:00 and a station registry — under an Italian open-data licence. From 10 February 2026 the Italian field separator changed from a comma to a pipe, which broke parsers written before that date. Records sit at site level with brand and operator as separate keys and an observed_at stamp on every row, nothing behind a login or an exchange licence is collected, and a site that disappears is confirmed across runs before it is called a closure.

A separator change is a silent break: the file downloads fine and the rows come out wrong.

Get a free sample See sample data

Free pilot on your own Spain and Italy list, returned in 24 hours. No card, no trial clock — and you keep the sample data either way.

spain_italy_sample.jsonl LIVE FEED

{"country_regime":"ES","fuel_grade":"gasolina 95 E5","price":1.499,"observed_at":"2026-09-23T10:00Z"} {"country_regime":"IT","snapshot_time":"08:00","price":1.739} {"file_format_version":"pipe separated","changed_on":"2026-02-10"}

illustrative sample rows · ES / ITtwo file habits · schema v1.0

Independence and trademarks. Actowiz Solutions is not affiliated with, endorsed by or connected to Spain and Italy or its owners. Spain and Italy and related marks belong to their respective owners, used here only to name the publicly accessible source this service collects from.

Our Data Powers

B2C Marketplace

amazon

D2C + Marketplace

NYKAA

D2C + Marketplace

Walmart

FMCG Marketplace

udaan

Food Delivery

Uber Eats

Quick Commerce

blinkit

Taxi Aggregator

Uber

E-Commerce

Tmall

Spain and Italy at a glance

How we handle Spain and Italy specifically

Platform-specific handling, not a generic retail template pointed at a different domain.

Spain: Keyless REST service
Spanish duty: Report price changes to the ministry
Italy: Two daily CSV files
Italian snapshot: Prices as at 08:00
10 Feb 2026: Separator changed to a pipe
Italian licence: Open data licence
Registry: Station anagraphic file, separate
Refresh: Daily files, plus site tier

Platform specifics

Two regimes, two file habits

These are the reasons a Spain and Italy dataset needs its own handling rather than a shared retail schema.

Format handling

A daily 08:00 snapshot is not an intraday series, and treating one file per day as continuous pricing overstates what Italy actually publishes.

snapshot_time where a file is a fixed-hour cut.
file_format_version including the separator in use.
registry_join linking price rows to station attributes.
country_regime so the two are never merged blindly.

Display rules, and what we do not do

Display rules

Italy's requirement to display an average price beside the station's own has been through the courts, so its current status is checked before any page relies on it rather than being asserted. See our France page.

Site level

Every figure stays attached to its site and its observation time rather than being rolled into an area average, as the fuel and energy hub describes.

What we do not do

Assume last year's file format still holds, merge a daily snapshot with intraday data, state a contested display rule as settled, or treat a registry file as a price file.

Scope

What we collect on Spain and Italy, and what we do not

The right column matters more than the left. Anyone can list fields; the limits are what tell you whether the dataset will hold up.

✅ What we collect

Country regime on every record
Snapshot time recorded
File format version tracked
Registry joined, not merged
Separator changes handled explicitly
Contested rules checked, not asserted
Brand and operator as separate keys
Site-level output
Daily and site refresh combined

❌ What we do not, and why

Assumed stable file formats
Snapshots merged with intraday
Contested rules stated as settled
Registry used as price source
Country regimes merged

Core Spain and Italy fields

The full dictionary is agreed during scoping. These are the fields specific to this platform.

Field	What it is on this platform
site_id	Official identifier
country_regime	ES, IT
brand / operator	Two keys
lat / lon / address	From registry
fuel_grade	Normalised, native label kept
price / currency_unit	EUR per litre
snapshot_time	Where fixed hour
file_format_version	Including separator
observed_at	Per record
self_service_flag	Where published
source	Per record

Use cases

What teams do with Spain and Italy data

Cross-border pricing

Iberian against Italian sites.

Motorway premiums

Concession sites against local.

Format resilience

Parsers that survive file changes.

Network mapping

Registry-backed site attributes.

The 24-hour sample — run on your sources, not ours

Send us a Spain and Italy item or category list. We run real collection against it and return the output within 24 hours, with the platform-specific fields populated so you can check them yourself rather than take our word for it.

Real extraction from your actual sources
Returned within 24 hours
Coverage and QA note included
You keep the data either way
No card, no trial clock
Named engineer on the call

Get my free sample Book a 20-min scoping call Reply within one business day. Reference calls available under NDA.

How we engage

Three ways to engage us

Same collection pipeline and QA underneath. The difference is who holds the schedule and how the data reaches you.

Managed service (most common)

We own the collection, the QA and the delivery. You receive clean data on a schedule and never touch a scraper.

Dedicated engineer assigned to your account
Site changes fixed by us, not reported to you
Scheduled delivery to your warehouse or S3
Named contact on Slack or email

Best fit: Teams who need the data, not the infrastructure.

API access

The same collection pipeline exposed as an authenticated REST endpoint your systems query directly.

On-demand and scheduled endpoints
Rate limits agreed to your load profile
Sandbox keys for integration testing
Versioned schema with deprecation notice

Best fit: Product and engineering teams building on live data.

One-time or project extraction

A defined pull for a specific question — market sizing, diligence, a pitch, a one-off audit.

Fixed scope agreed in writing upfront
Single delivery with full QA report
Methodology documented for your records
Converts to managed if you want continuity

Best fit: Research, strategy and diligence work with a deadline.

Pricing

Every engagement is quoted individually, because the honest answer depends on your scope: how many sources, how many records, how often, and how the data reaches you. We scope it with you, run a free pilot on your own sources, and then quote a fixed monthly figure — no per-request metering and no overage billing when volumes move. Request a quote and you will have a number after one call.

Spain and Italy is usually collected alongside its competitors

Almost nobody buys a single platform in isolation. Spain and Italy data becomes useful when it sits next to the competitor set on one schema, refreshed on one schedule, so a price index or availability comparison is genuinely like-for-like.

That is what fuel & energy data covers, and a Spain and Italy-only engagement can be expanded into it without rebuilding. If you already know you need several platforms, start there instead — it is the same pipeline and usually the better scoping conversation.

FAQ

Spain and Italy data scraping: frequently asked questions

Platform-specific questions, including what cannot be collected here.

The ministry REST service is free and keyless.

The published file is a daily snapshot at a fixed hour.

The Italian file separator moved from a comma to a pipe.

No. The regime field stays on every record.

It has been litigated. We check its status rather than assert it.

It depends on countries, sites and refresh.

Talk to us.

See real Spain and Italy data before you commit to anything

Send us an item or category list. We return the output within 24 hours with the platform-specific fields populated.

Get a free sample Talk to an engineer

Free pilot, no card, no obligation. If we cannot collect a field you need on this platform, the sample shows you that too.

Hear It Directly from Our Clients

Watch how businesses like yours are using Actowiz data to drive growth.

▶

1 min

★★★★★

"Actowiz Solutions offered exceptional support with transparency and guidance throughout. Anna and Saga made the process easy for a non-technical user like me. Great service, fair pricing!"

Thomas Galido

Co-Founder / Head of Product at Upright Data Inc.

▶

2 min

★★★★★

"Actowiz delivered impeccable results for our company. Their team ensured data accuracy and on-time delivery. The competitive intelligence completely transformed our pricing strategy."

Iulen Ibanez

CEO / Datacy.es

▶

1:30

★★★★★

"What impressed me most was the speed — we went from requirement to production data in under 48 hours. The API integration was seamless and the support team is always responsive."

Febbin Chacko

-Fin, Small Business Owner