Product updates

Changelog

A readable summary of what we improve in Apiverket. We keep this focused on changes that affect reliability, the dashboard, API behavior, documentation, and developer experience.

12recent updates published
280+public endpoints monitored
45+Swedish data sources covered
Geography

Lantmäteriet geo data added

Apiverket now exposes Swedish elevation, administrative geography, and official place names through clean JSON endpoints.

  • Elevation lookups use Lantmäteriet Markhöjd Direkt behind `/v1/geo/elevation`.
  • Municipality, county, and country endpoints use Lantmäteriet Kommun, Län och Rike Direkt.
  • Place-name search and references use Lantmäteriet Ortnamn Direkt v2.2.
  • Responses use WGS84-friendly inputs and stable Apiverket metadata while keeping raw source geometry out of default responses.
Docs

SCB statistics are easier to explore

It is now easier to see where Apiverket's SCB statistics come from and how to try the right examples.

  • SCB discovery shows the source tables behind statistics endpoints, with supported dimensions, filters, and examples.
  • Statistics guides now point to the canonical population, CPI, GDP, wages, and SCB table-registry endpoints.
  • The guide explains how source metadata such as table ID, table title, and period maps clean JSON back to SCB's PxWeb tables.
API UX

Clearer migration help for older endpoint paths

Older or placeholder endpoint paths now return more useful guidance instead of leaving integrations stuck at a bare 404 or confusing quota message.

  • Moved endpoint paths now point to the current endpoint and include runnable examples.
  • Known deprecated paths include deprecation headers so clients can detect and migrate them programmatically.
  • Daily quota errors now state which tier the API key is authenticated as and show the matching daily limit.
Reliability

More reliable traffic and infrastructure data

We improved how Apiverket handles Trafikverket-backed infrastructure endpoints when an external source is slow or temporarily unavailable.

  • Traffic cameras, parking, speed limits, traffic flow, travel times, rest areas, rail crossings, road conditions, and pavement data now have stronger failure protection.
  • When recent cached data is available, selected endpoints can keep responding instead of failing immediately.
  • Endpoints that use curated example data are now marked more clearly, so it is easier to understand what is live data and what is a documented example.
  • Endpoint checks are now better at separating real problems from documented example data, which helps us improve the platform in the right order.
Company data

Broader company lookup coverage

Organisation-number lookups now use SCB Företagsregister as a fallback when Bolagsverket does not return a match.

  • Company lookup keeps the same API shape, but can find more active Swedish companies.
  • Responses show whether the data came from Bolagsverket or SCB Företagsregister.
  • Company search remains SCB-based and keeps its separate daily search quota.
Reliability

Broader endpoint checks before users find problems

We expanded our endpoint smoke tests so published examples are checked regularly with working test values.

  • All public API examples are now checked from a canonical smoke-test list.
  • Broken routes, unexpected 404s, timeouts, and server errors are easier to catch before they reach users.
  • Regular monitoring helps us compare API health over time and spot regressions earlier.
Stability

More resilient responses when source APIs struggle

External sources can occasionally be slow or unavailable. Apiverket now handles those cases more gracefully.

  • Popular upstream sources have clearer timeouts and temporary failure protection.
  • When recent cached data is available, selected endpoints can keep responding instead of failing immediately.
  • Error messages are clearer about whether a Swedish source is temporarily unavailable.
Support

Faster support for integration problems

We improved the signals we use to notice when an integration is getting repeated errors, so support can be more proactive.

  • Repeated 404s, quota loops, and temporary source errors are easier to understand.
  • Support can more quickly tell whether a problem is a wrong endpoint, a quota issue, or a source outage.
  • The goal is faster, more useful help when an API integration gets stuck.
Dashboard

Account and billing settings in the dashboard

Logged-in users now have a dedicated settings area for practical account and billing tasks.

  • Users can review account details and update safe profile settings.
  • Billing actions such as invoices, receipts, payment method changes, plan changes, and cancellation are handled through Stripe.
  • Email preferences are visible and can be updated from the dashboard.
API UX

Clearer company-search quota guidance

Company search now gives clearer guidance when a daily search quota has been reached.

  • The API now explains when clients should pause until the next reset instead of retrying in a loop.
  • Dashboard usage shows company-search quota information when it is relevant.
  • This makes rate-limit handling easier for users building automated company lookup workflows.
Operations

Public status page and source health monitoring

We added a public status page and deeper source monitoring across Swedish data providers.

  • The public status page shows the current health of Apiverket and upstream data sources.
  • Source checks help us separate Apiverket issues from temporary upstream outages.
  • Health history gives better context when diagnosing reliability problems.
Docs

More guides, docs, and discoverability

We improved public documentation so new users can understand what Apiverket offers faster.

  • Added practical guides for weather data, company data, and SCB statistics.
  • Improved public API metadata for search engines and API directories.
  • Added Swedish landing and guide pages for local users.
© 2026 Apiverket.se Docs · Console · Privacy