API terms of use

Last updated 30 July 2026.

These terms govern access to the Bojakt API. By requesting or using a key you accept them on behalf of the organisation the key was issued to. They are in addition to any written agreement between us; where the two conflict, the written agreement wins.

1. Who we are

The Bojakt API is operated by Ketryon AB, org.nr 559551-1030, Gamla Tullgatan 1, 632 17 Eskilstuna, Sweden — bojakt.se@gmail.com. Ketryon AB is your counterparty.

2. What the API gives you

Read access to rental listings published on bojakt by their landlords, and to notifications when new ones appear. The API is read-only: there is no endpoint that creates or modifies a listing.

It does not include bojakt's aggregated third-party inventory. bojakt's website also shows listings collected from other sources; those are not served through the API and are not licensed to you here. If you need them, licence them from their sources.

3. Your licence

For as long as your key is valid, we grant you a non-exclusive, non-transferable, revocable licence to retrieve listings via the API and to display and redistribute them in your own products and services, including the listing photographs, subject to the conditions below.

You may not sublicense the data as a data feed to further parties, or present it in a way that implies bojakt endorses you.

4. Removals must propagate

This is the condition the licence depends on. When a landlord removes a listing, or we remove it, it must stop appearing on your surfaces too. In practice:

• Re-check listings you display at least every 24 hours. A listing that returns 404, or is absent from /v1/listings, is withdrawn — remove it within 24 hours.
• Do not keep a permanent copy of a withdrawn listing or its photographs, and do not serve them from your own cache after removal.
• Do not present a withdrawn listing as available, and do not keep contacting the landlord about it.

We tell landlords their listing stops being distributed when they take it down. This clause is how we keep that promise.

5. Accuracy, and what the data is not

Listings are written by landlords and reviewed by us before publication, but we are not a party to any tenancy and we do not warrant that a listing is accurate, current or still available. The API is provided as-is. You are responsible for what you publish from it, including any consumer-law obligations that attach to your own surfaces.

municipality is populated for some listings only. Check /v1/cities before assuming coverage in a location.

6. Personal data

The API deliberately exposes no personal data — no landlord or seeker names, emails, phone numbers, or search criteria. You must not attempt to re-identify individuals from listing data, combine it with other sources for that purpose, or use it to build profiles of landlords or tenants.

For personal data you process in your own products, you are the controller and it is your responsibility.

7. Keys, limits and fair use

• Keys identify your organisation. Keep them secret, server-side, and out of client applications and public repositories. Tell us immediately if one is exposed and we will revoke it.
• Use a separate key per environment, and rotate rather than share.
• Respect the rate limit and monthly quota shown on your dashboard. Back off on 429. Page with cursor and use since for incremental syncs rather than re-downloading the catalogue; page size is capped at 200.
• Do not attempt to circumvent limits, probe for other partners' data, or access the database directly.

8. Suspension and termination

Either of us may end this at any time — you by stopping use, us by revoking your keys. We may suspend access without notice where we reasonably believe there is a security problem, a breach of §4 or §6, or use that threatens the service. On termination, stop using the API and remove listings obtained through it from your surfaces within 30 days.

9. Availability and changes to the API

There is no service level commitment. We may change, deprecate or withdraw endpoints. Breaking changes to /v1 will be announced by email to your registered contact at least 60 days in advance; additive changes — new fields, new endpoints — may ship at any time, so parse defensively and ignore fields you do not recognise. The OpenAPI document is the contract; diffing it in your CI is the intended way to notice a change.

10. Liability

To the extent permitted by law, we are not liable for indirect or consequential loss, lost profits, or loss of data arising from use of the API, and our total liability is limited to any fees you have paid us for API access in the twelve months before the claim. Nothing here limits liability that cannot be limited by law.

11. Changes and governing law

We may update these terms; material changes are announced in advance to your registered contact. Swedish law applies, and disputes are heard by Swedish courts with Eskilstuna tingsrätt as the court of first instance.

Questions about any of this — including whether an intended use is allowed — go to bojakt.se@gmail.com. Asking first is always cheaper than a revoked key.