Hemnet Scraper & Authorized Swedish Property Data Access

Hemnet Property Data Starts With the Access Path

Hemnet.se is provided by Hemnet AB. Hemnet Group AB (publ) is the parent company, with the group’s core operations carried out through Hemnet AB. Hemnet Group describes Hemnet as Sweden’s leading housing platform.

For a property-data team, the useful first question is not: “Can we scrape Hemnet?” It is: “Does Hemnet’s official BostadsAPI, another contractual arrangement, or an approved alternative source already support the records and use case we need?”

A useful project should define:

• active listings, sold properties, or both
• Swedish municipality/county/geography
• property/housing forms
• asking-price fields
• final-sale-price fields
• monthly fee requirements
• living, supplementary, and plot-area fields
• broker/agency fields
• energy fields
• historical versus current need
• one-time versus recurring use
• downstream application
• source/access rights
• whether AI/ML use is contemplated

NenoData’s current Real Estate Data Scraping service similarly treats source, fields, geography, access conditions, intended use, storage, and delivery as scope questions that are confirmed before implementation rather than assumed.

Hemnet Has an Official Broker API

Hemnet publishes an official first-party API called BostadsAPI. Current documentation explicitly describes it as Hemnet’s Broker API. Its purpose is to let brokers, broker agencies, and broker systems provide Hemnet with data or query Hemnet for data. See the official BostadsAPI documentation.

BostadsAPI includes:

Do not position BostadsAPI as anonymous, self-service public marketplace access.

BostadsAPI Is Not an Open Public Marketplace API

The existence of BostadsAPI does not establish unrestricted third-party read access to the full Hemnet marketplace. Current documentation contains account-context resources and is expressly contract restricted.

Hemnet operates an official contract-restricted Broker API, but unrestricted public bulk read access to the entire Hemnet marketplace was not verified.

Do not say:

• Hemnet has no API.
• Hemnet provides an unrestricted public marketplace API.
• NenoData already has BostadsAPI credentials.
• BostadsAPI can export every Hemnet listing.
• Anyone can create a BostadsAPI key.

Before implementation around BostadsAPI, confirm:

Official BostadsAPI vs Third-Party “Hemnet APIs”

Third-party products may market themselves as Hemnet APIs, scraper APIs, extraction APIs, or parser APIs.

Do not describe third-party extraction products as BostadsAPI.

What Hemnet Data May Be Relevant?

The exact schema depends on the approved source, contract, account context, record type, and project scope.

This is an illustrative schema. It does not establish current NenoData Hemnet production coverage. It does not mean every field is present on every record or through every authorized account.

Active Listing and Sold Record Are Different Data Objects

A useful Hemnet model should distinguish the property entity, its active listing phase, market-state observations, and the eventual sale event.

Do not flatten active-listing and sale-event semantics into one record without retaining event type and provenance.

Asking Price and Slutpris Must Stay Separate

Slutpris is the reported final sale price for an eligible sold-property record. See current Hemnet sold-property pages for current concepts including:

A source-aware schema may include:

Do not collapse these into one generic price. Do not treat slutpris as equivalent to every possible authoritative Swedish property-transaction source.

Percentage Above or Below Asking Is a Derived Sale Metric

Current Hemnet sold records can display sale-price difference percentages such as a positive percentage, a negative percentage, or zero difference.

A structured record may preserve the source-displayed percentage. Alternatively, where rights and fields permit, NenoData may derive a percentage from approved price values.

Potential fields:

If NenoData calculates the metric:

• define the formula
• preserve source inputs
• mark the result as derived
• do not imply it was source-provided

Public Slutpris Coverage Is Conditional

Hemnet’s current help documentation says sold-price publication is conditional. Historically, sold-price pages applied to listings that had appeared as upcoming or for sale on Hemnet where buyer and seller agreed to publication.

Following an April 2026 update, Hemnet also supports certain sales completed outside Hemnet where a public sold price has been reported to Hemnet under the applicable conditions. This applies to qualifying sold-price information reported from late March 2026 onward and does not retroactively create public sold-price pages for every older sale.

Therefore:

• not every Swedish property transaction should be assumed to appear on Hemnet
• public Hemnet sold-price visibility is not exhaustive transaction coverage
• a Hemnet sold record is not equivalent to a complete Swedish transaction registry
• sold-page absence must not be treated as evidence that no sale occurred

Where broader or authoritative transaction coverage is needed, evaluate an appropriate approved transaction/property-record source separately. NenoData’s Real Estate Transaction Data service contextually for that requirement.

Avgift Is Not Rent

Hemnet sold apartment records can display monthly fees expressed in SEK per month. For relevant Swedish cooperative-apartment records, this is a distinct cost concept.

A useful schema may include:

Do not merge avgift into:

Preserving avgift separately is important for meaningful apartment comparison.

Swedish Housing Form and Tenure Need Source-Aware Mapping

A generic property-type field can erase important Swedish semantics.

Potential source concepts may include:

The schema should distinguish, where supported, physical/property form from tenure/ownership structure. Preserve the original source term alongside normalized categories when useful.

Do not force Swedish concepts into unrelated U.S.-style ownership categories.

Boarea, Biarea, and Tomtarea Should Not Be Collapsed

Swedish property records may contain several distinct area concepts.

A normalized schema may use:

Source records may also display combined visual forms such as living plus supplementary area.

• Do not combine all areas into one generic field.
• Do not add boarea + biarea unless the business requirement explicitly calls for a derived total, the formula is documented, the output is marked derived, and original source values remain available.
• Never add tomtarea to interior/living-area values.

SEK and SEK/m² Need Separate Fields

Potential price fields include:

Preserve:

• Do not overwrite total price with SEK/m².
• Do not calculate SEK/m² using plot area where the business requirement expects living area.

NenoData’s Data Cleaning & Standardization service supports agreed field mapping, transformation rules, and validation for SEK and area fields.

Market State Is Different From Sale State

BostadsAPI documentation includes market-state concepts.

Where supported by the approved API/source, preserve the source state. Keep market state separate from:

Do not reduce every lifecycle state to a single active = true/false field if doing so loses source meaning.

Energy Fields Are Source-Dependent

A Swedish property workflow may require energy/building fields. Use only fields that are actually supported by the approved BostadsAPI account, customer-controlled data, or another approved source.

Potential energy/building fields should remain source-dependent and confirmed during scoping.

Do not promise:

Missing values should remain missing or unresolved.

Hemnet’s Scraping Restriction Is Explicit

Treat this as a substantive source/access restriction—not an anti-bot engineering, request throttling, CAPTCHA, rendering, or proxy-infrastructure issue.

NenoData does not market:

Hemnet Also Restricts AI/ML Input Use

A customer asking for Hemnet-related data for these purposes requires specific rights review:

Do not position Hemnet source content as:

Do not infer permission from the fact that Hemnet itself may launch authorized AI integrations. Hemnet-controlled or Hemnet-authorized AI use does not establish third-party rights.

Broker and Agency Data Need Separate Review

Hemnet is broker-centric, and BostadsAPI includes broker and broker-agency resources.

Brokerage/agency identity may support:

Personal contact information is a separate data class. Hemnet’s terms also prohibit using the platform to collect or store personal information about others without consent.

Do not make these a headline proposition:

Any personal/contact-data requirement needs separate review of:

Authorized Hemnet Data Paths NenoData Can Evaluate

NenoData’s Multi-Source Data Aggregation service supports agreed external and customer-authorized sources rather than arbitrary source use.

The page must remain commercially useful when BostadsAPI does not fit the requirement.

Active-to-Sold Matching Should Be Scoped, Not Assumed

A common business requirement is to connect an active listing to its corresponding sold record.

This may support:

Matching is not automatically perfect. Relevant fields may include:

Use NenoData’s Entity Resolution capabilities only as a scoped matching workflow. Note: whether Hemnet-origin data can be processed through a particular AI/ML method must still satisfy the applicable Hemnet contractual/source rights.

Define:

Do not claim:

One-Time Dataset or Recurring Observation

Where the approved source arrangement permits repeated data access and retention, a workflow may be one-time or recurring.

Repeated access must remain contractually permitted. Retention must remain permitted.

Do not claim:

Delivery Does Not Expand Source Rights

NenoData’s Custom Data Pipelines capability can support approved workflows involving:

• CSV
• Excel
• JSON
• API-ready records
• databases
• warehouses
• webhooks
• scheduled workflows

For Hemnet-related data, confirm:

1. 1.contractual/API rights
2. 2.supported records
3. 3.permitted storage
4. 4.permitted transformation
5. 5.retention
6. 6.public versus internal use
7. 7.redistribution
8. 8.AI/ML restrictions
9. 9.privacy requirements
10. 10.final destination
11. 11.recurring cadence

“API-ready” means NenoData can structure approved records for downstream programmatic use. It does not mean NenoData provides unrestricted BostadsAPI access.

How an Authorized Hemnet Data Workflow Would Work

1. 1

   Define the business requirement

   Specify active listings, sold properties, or both; Swedish geography; property/housing forms; asking-price fields; slutpris; monthly fees; area fields; broker fields; energy fields; historical/current requirement; intended use; AI/ML involvement; and destination.

2. 2

   Evaluate BostadsAPI eligibility

   Confirm signed Hemnet contract, API/account access, authorized API keys, relevant listing/account scope, supported resource types, storage rights, and downstream-use rights.

3. 3

   Select the approved source path

   Potential routes: BostadsAPI, explicit Hemnet permission, broker/customer-owned data, approved brokerage feed, licensed Swedish property data, approved transaction/property-record source, or customer-supplied files.

4. 4

   Define the property model

   Separate property, active listing, market-state observation, sale event, and broker/agency into distinct schema objects.

5. 5

   Define price semantics

   Preserve asking price, slutpris, SEK, SEK/m², sale-versus-asking percentage, and sold date as distinct fields.

6. 6

   Define area and fee semantics

   Preserve boarea, biarea, tomtarea, and monthly avgift in their original source representation.

7. 7

   Define matching logic

   Where active and sold records need linking, agree match identifiers, address fields, property attributes, broker fields, deterministic/fuzzy logic, confidence thresholds, and exception review.

8. 8

   Ingest through the approved source

   Use only the contractually permitted, customer-controlled, licensed, or explicitly authorized source path.

9. 9

   Normalize and validate

   Apply agreed rules for SEK, area units, property/housing form, tenure, monthly fee, market state, sale state, source attribution, duplicates, matching, missing fields, and exceptions.

10. 10

    Deliver within rights

    Prepare the approved file, API-ready structure, database, warehouse, webhook, or scheduled/recurring workflow within the confirmed source rights.

Potential Business Requirements

These are examples of customer needs, not proof of blanket rights to Hemnet content.

Why NenoData Is Relevant to a Hemnet Requirement

NenoData Is Not Affiliated With Hemnet

NenoData does not claim affiliation with Hemnet, partnership with Hemnet AB, partnership with Hemnet Group AB, a signed Hemnet contract, BostadsAPI credentials, marketplace-wide API access, unrestricted Hemnet rights, an existing Hemnet dataset, historical Hemnet coverage, or authorized-scraper status. Only state such a relationship if separately documented.

Frequently Asked Questions