# Denmark Fuel Prices (`scrapme/denmark-fuel-prices`) Actor

Live pump prices for petrol and diesel at 1,600+ Danish fuel stations (OK, Q8, F24, Shell, OIL!, Uno-X, Go'on) from the official price APIs, in one clean dataset.

- **URL**: https://apify.com/scrapme/denmark-fuel-prices.md
- **Developed by:** [MDBBusiness](https://apify.com/scrapme) (community)
- **Categories:** Travel, E-commerce
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$0.50 / 1,000 price rows

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Denmark Fuel Prices

Get live pump prices for petrol and diesel at **1,600+ Danish fuel stations** in one clean dataset. The Actor reads the official price APIs of OK, Q8, F24, Shell, OIL! tank & go, Uno-X and Go'on and puts everything into the same format.

### Why this Actor?

Since 1 January 2026, Danish fuel companies must publish their current pump prices for every station through a public API (the Danish price-marking order, § 16 a). But there is no national register: every brand has its own API with its own format. This Actor does the work of reading all of them and joining the data for you.

### What you get

- Current price per liter for every fuel product at every station
- Brand, station ID, address, postal code and (for most brands) GPS coordinates
- Fuel category (`petrol`, `diesel`, `other`) and octane
- Time of the last price change, as reported by the brand
- Optional: distance to a location you choose, sorted nearest first

### Use cases

- **Fleets and haulers**: find the cheapest diesel near your routes and depots
- **Price comparison apps and websites**: one feed instead of seven integrations
- **Analysts and journalists**: track price levels and differences between brands and regions over time (schedule the Actor to run every hour or every day)

### Supported brands

| Brand | Stations (Oct 2026) | Coordinates |
|---|---|---|
| OK | ~690 | Yes |
| Q8 | ~100 | Yes\* |
| F24 | ~140 | Yes\* |
| Shell | ~210 | Yes |
| OIL! tank & go | ~70 | Yes |
| Uno-X | ~280 | Yes |
| Go'on | ~190 | Yes |

\* Q8 and F24 do not include coordinates in their price API. The Actor adds them from Q8's own public station finder (q8.dk/find-station) by matching the address.

**Not yet supported:** Circle K / INGO. Support may be added later.

### Input

| Field | Description |
|---|---|
| `brands` | Which brands to include. Default: all. |
| `fuelCategories` | `petrol`, `diesel` and/or `other` (e.g. AdBlue). Default: petrol and diesel. |
| `postalCodes` | Only stations in these postal codes, e.g. `["2100", "8000"]`. |
| `latitude`, `longitude` | Optional location. Adds `distanceKm` and sorts by nearest. Stations without coordinates are left out when a location is set. |
| `radiusKm` | Only stations within this distance of the location. `0` = no limit. |
| `maxResults` | Maximum number of rows. `0` = no limit. |

Example: cheapest diesel within 15 km of Aarhus city center:

```json
{
    "latitude": 56.1572,
    "longitude": 10.2107,
    "radiusKm": 15,
    "fuelCategories": ["diesel"]
}
```

### Output

One row per station and product. Example:

```json
{
    "brand": "Shell",
    "stationId": "D044",
    "stationName": null,
    "address": "VANDVEJEN 5, 8000 ÅRHUS",
    "street": "VANDVEJEN 5",
    "postalCode": "8000",
    "city": "ÅRHUS",
    "latitude": 56.142572,
    "longitude": 10.230662,
    "fuelCategory": "diesel",
    "octane": null,
    "productName": "FuelSave Diesel",
    "pricePerLiter": 20.39,
    "currency": "DKK",
    "lastUpdated": "2026-10-20T11:00:00.000",
    "source": "https://shellpumpepriser.geoapp.me/v1/prices",
    "distanceKm": 2.04,
    "scrapedAt": "2026-10-20T20:25:30+00:00"
}
```

You can download the dataset as JSON, CSV, Excel or XML, or read it through the Apify API.

### Good to know

- Prices are exactly what each brand publishes in its official API. Brands update their APIs when the pump price changes, but the Actor cannot guarantee that the price at the pump is the same at the moment you arrive.
- `lastUpdated` is passed on as the brand reports it. Brands use different time formats, and some leave out the time zone.
- For Q8 and F24, street, city and coordinates come from Q8's station finder. If a station cannot be matched, those fields are empty, but `address` and `postalCode` are always filled.
- EV charging prices (per kWh) are not included.
- The Actor makes about a dozen requests per run and waits at least 1 second between them.
- Uno-X and Go'on allow one request per 30 seconds. If many runs start at the same moment, one of these two brands can be skipped in a run. The run log says which brand was skipped.

### Data sources

All data comes from the brands' own public price APIs:

- OK: `mobility-prices.ok.dk`
- Q8 / F24: `beta.q8.dk` (prices) and `www.q8.dk/find-station` (coordinates)
- Shell: `shellpumpepriser.geoapp.me` (linked from shellservice.dk)
- OIL! tank & go: `apim-fuel-prices-prod.azure-api.net`
- Uno-X: `api.unoxmobility.net`
- Go'on: `goon.nu`

The Actor does not collect personal data. Station owner names are left out on purpose.

# Actor input Schema

## `brands` (type: `array`):

Which fuel brands to include. Leave empty for all supported brands.

## `fuelCategories` (type: `array`):

petrol = gasoline (95/98/100), diesel = diesel and HVO, other = e.g. AdBlue.

## `postalCodes` (type: `array`):

Only return stations in these Danish postal codes, e.g. 2100 or 8000. Leave empty for the whole country.

## `latitude` (type: `number`):

Optional. With longitude, adds distance in km and sorts by nearest station. Stations without coordinates are left out when a location is set.

## `longitude` (type: `number`):

Optional. Use together with latitude.

## `radiusKm` (type: `integer`):

Optional. Only stations within this distance of the location. 0 = no limit.

## `maxResults` (type: `integer`):

Maximum number of price rows. 0 = no limit.

## Actor input object example

```json
{
  "brands": [
    "OK",
    "Q8",
    "F24",
    "Shell",
    "OIL!",
    "Uno-X",
    "Go'on"
  ],
  "fuelCategories": [
    "petrol",
    "diesel"
  ],
  "postalCodes": [],
  "radiusKm": 0,
  "maxResults": 0
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("scrapme/denmark-fuel-prices").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("scrapme/denmark-fuel-prices").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call scrapme/denmark-fuel-prices --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,scrapme/denmark-fuel-prices"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/geTmBq8aIadxRyW8q/builds/lTA4haaEJkUKF0sbS/openapi.json