Heimster

Heimster is a Swiss software platform for real‑estate agents and marketers, offering CRM, marketing, portal integration, digital sales and rental processes, and AI automation. It also runs a free property portal for seekers, serving the full value chain for Swiss real‑estate professionals.

Heimster is listed with 16 APIs on the APIs.io network, including Analytics API, Anlageobjekte API, Applications API, and 13 more. Tagged areas include Real Estate, Software, CRM, Artificial Intelligence, and Swiss.

The Heimster catalog on APIs.io includes 1 event-driven AsyncAPI specification, 1 JSON-LD context, and 1 Spectral governance ruleset.

Heimster’s developer surface includes API reference, getting-started guide, pricing, signup flow, and 18 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

39.0/100 thin Agent 44/100 agent ready Full breakdown ↓
scored 2026-11-13 · rubric v0.28.0 · Show this score on your site →

AccessPaid

16 APIs 1 MCP Servers

Real Estate Software CRM Artificial Intelligence Swiss

Kin Score

Kin Score How this is scored →
scored 2026-11-13 · rubric v0.28.0

Composite quality — 39.0/100 · thin

Contract Quality 6.8 / 21

Developer Ergonomics 4.9 / 17

Access Clarity 10.5 / 17

Operational Transparency 1.8 / 11

Contract Governance 2.2 / 10

Discoverability 6.0 / 9

Regulatory Posture 3.4 / 15

Agent readiness — 44/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 12 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 6 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 6 / 6

Protected Resource Metadata 5 / 5

Registration Without a Human 6 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/heimster-ch/"><img src="https://apis.io/badge/heimster-ch/card.svg" alt="Heimster on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author Ask about this →
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented) Ask about this →
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes Ask about this →
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0 Ask about this →
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented) Ask about this →
Documented Reversibility +6 pts — a reversal operation in the contract, graded up when a window is documented too Ask about this →

5 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 32.0 — up to +17.0 composite points Ask about this →
Developer Ergonomics scores 28.6 — up to +14.3 composite points Ask about this →
Operational Transparency scores 16.7 — up to +10.8 composite points Ask about this →

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Not sure how this applies to your stack? Ask about any one item. Kin Lane reads every question, looks at your profile and your situation, and replies with what a fix would take — scoped to that one area, priced up front, yours whether you ship it or not. Ask a question →

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/heimster-ch/apis.yml: open an issue on github.com/api-evangelist/heimster-ch to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 4

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

Model Context Protocol (MCP)

measured — observed by APIs.io (documented)

OAuth 2.0 Protected Resource Metadata

measured — observed by APIs.io (verified)

Dynamic Client Registration

measured — observed by APIs.io (published)

OpenAPI

measured — observed by APIs.io (published)

APIs 16

Individual APIs this provider publishes, each with its own machine-readable definition.

Heimster Analytics API

The Analytics API from Heimster — 1 operation(s) for analytics.

Heimster Anlageobjekte API

The Anlageobjekte API from Heimster — 2 operation(s) for anlageobjekte.

Heimster Applications API

The Applications API from Heimster — 2 operation(s) for applications.

Heimster Contacts API

The Contacts API from Heimster — 3 operation(s) for contacts.

Heimster Email API

The Email API from Heimster — 1 operation(s) for email.

Heimster Export API

The Export API from Heimster — 1 operation(s) for export.

Heimster Follow Ups API

The Follow Ups API from Heimster — 1 operation(s) for follow ups.

Heimster Interested Parties API

The Interested Parties API from Heimster — 1 operation(s) for interested parties.

Heimster Leads API

The Leads API from Heimster — 1 operation(s) for leads.

Heimster Listings API

The Listings API from Heimster — 3 operation(s) for listings.

Heimster Objects API

The Objects API from Heimster — 3 operation(s) for objects.

Heimster Opportunities API

The Opportunities API from Heimster — 1 operation(s) for opportunities.

Heimster Projects API

The Projects API from Heimster — 2 operation(s) for projects.

Heimster Tasks API

The Tasks API from Heimster — 1 operation(s) for tasks.

Heimster Telephony API

The Telephony API from Heimster — 3 operation(s) for telephony.

Heimster Viewings API

The Viewings API from Heimster — 1 operation(s) for viewings.

Scroll for all 16

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Heimster MCP Server

Remote MCP server at heimster.ch requiring an API key.

MCP SERVER

Heimster API pricing

Prices published by Heimster, read 2026-11-11 from heimster.ch/en/preise.

Plan	Price
Basis	CHF 99 per user per month, excl. VAT
Projects	CHF 99 per user per month, excl. VAT
Investment assets	CHF 99 per user per month, excl. VAT

Plan details, limits and sources →

Pricing Plans 1

Published pricing tiers and plan structures.

Heimster Plans Pricing

3 plans

PLANS

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Heimster Ch Webhooks

ASYNCAPI

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Heimster Ch Context

52 classes · 117 properties

JSON-LD

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs. Counts are the severity each rule declares, not results of running them.

Heimster API Rules

45 rules · 42 error-severity 2 warn-severity 1 info-severity

SPECTRAL

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Heimster Openapi Overlay

0 actions · update

UNRECORDED

JSON Schema 6

Standalone JSON Schema definitions for this provider's data models.

PatchApiV1ContactsIdRequest

13 properties

JSON SCHEMA

PostApiV1ContactsIdActivitiesRequest

8 properties

JSON SCHEMA

PostApiV1ContactsResponse

2 properties

JSON SCHEMA

PostApiV1ObjectsRequest

16 properties

JSON SCHEMA

PostApiV1TelephonyCallsRequest

13 properties

JSON SCHEMA

PostApiV1ViewingsRequest

15 properties

JSON SCHEMA

Security Posture 1

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Heimster Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Get Started 4

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

Login

SignUp

SignUp

Documentation 1

Reference material describing how the API behaves

APIReference

APIReference

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

MCPServer

MCPServer

WellKnown

WellKnown

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Spectral

JSONLD

Vocabulary

Webhooks

DataModel

Conformance

Access & Security 2

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Security

Security

Commercial 4

Pricing, plans, and the legal terms of use

Plans

Pricing

PrivacyPolicy

TermsOfService

Company 1

The organization behind the API

Website

Website

Other 1

Properties that don't map to a standard resource type

Hosts

Hosts

Source (apis.yml)

aid: heimster-ch
name: Heimster
accessModel:
  pricing: paid
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Paid
  confidence: low
  source:
  - plans
  - security
  generated: '2026-11-13'
  method: derived
image: https://heimster.ch/og/page/home.png?v=mqjd3f
description: Heimster is a Swiss software platform for real‑estate agents and marketers, offering CRM, marketing, portal integration,
  digital sales and rental processes, and AI automation. It also runs a free property portal for seekers, serving the full
  value chain for Swiss real‑estate professionals.
url: https://artifacts.apis.io/heimster-ch/apis.yml
x-type: company
x-source: harvest:mcp-registry
x-tier: profiled
x-tier-reason: enrichment pass 2026-11-11 (modular-v1; was harvest)
specificationVersion: '0.20'
created: '2026-11-11'
modified: '2026-11-11'
tags:
- Real Estate
- Software
- CRM
- Artificial Intelligence
- Swiss
tags_raw:
- RealEstate
- Software
- CRM
- AI
- Swiss
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Plans
  url: plans/heimster-ch-plans-pricing.yml
- type: Spectral
  url: rules/heimster-ch-rules.yml
- type: JSONLD
  url: json-ld/heimster-ch-context.jsonld
- type: Vocabulary
  url: vocabulary/heimster-ch-vocabulary.yml
- type: Webhooks
  url: asyncapi/heimster-ch-webhooks.yml
- type: DataModel
  url: data-model/heimster-ch-data-model.yml
- type: Conformance
  url: conformance/heimster-ch-conformance.yml
- type: LLMsTxt
  url: llms/heimster-ch-llms.txt
- type: MCPServer
  url: mcp/heimster-ch-mcp.yml
- type: WellKnown
  url: well-known/heimster-ch-well-known.yml
- type: Hosts
  url: hosts/heimster-ch-hosts.yml
- type: APIReference
  url: https://heimster.ch/en/developers
- type: DomainSecurity
  url: security/heimster-ch-domain-security.yml
- type: Website
  url: https://heimster.ch/
- type: DeveloperPortal
  url: https://heimster.ch/developers
- type: GettingStarted
  url: https://heimster.ch/en/register/professional
- type: Login
  url: https://heimster.ch/en/login
- type: Pricing
  url: https://heimster.ch/en/preise
- type: PrivacyPolicy
  url: https://heimster.ch/en/privacy
- type: Security
  url: https://heimster.ch/en/sicherheit
- type: SignUp
  url: https://heimster.ch/en/register/professional
- type: TermsOfService
  url: https://heimster.ch/en/terms
apis:
- aid: heimster-ch:heimster-ch-analytics-api
  name: Heimster Analytics API
  description: The Analytics API from Heimster — 1 operation(s) for analytics.
  humanURL: https://heimster.ch/developers
  baseURL: https://heimster.ch/api/v1
  tags:
  - Analytics
  properties:
  - type: OpenAPI
    url: openapi/heimster-ch-analytics-api-openapi.yml
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-telephony-calls-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-objects-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-contacts-response-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-contacts-id-activities-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-viewings-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-patch-api-v1-contacts-id-request-schema.json
- aid: heimster-ch:heimster-ch-anlageobjekte-api
  name: Heimster Anlageobjekte API
  description: The Anlageobjekte API from Heimster — 2 operation(s) for anlageobjekte.
  humanURL: https://heimster.ch/developers
  baseURL: https://heimster.ch/api/v1
  tags:
  - Anlageobjekte
  properties:
  - type: OpenAPI
    url: openapi/heimster-ch-anlageobjekte-api-openapi.yml
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-telephony-calls-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-objects-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-contacts-response-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-contacts-id-activities-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-viewings-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-patch-api-v1-contacts-id-request-schema.json
- aid: heimster-ch:heimster-ch-applications-api
  name: Heimster Applications API
  description: The Applications API from Heimster — 2 operation(s) for applications.
  humanURL: https://heimster.ch/developers
  baseURL: https://heimster.ch/api/v1
  tags:
  - Application
  tags_raw:
  - Applications
  properties:
  - type: OpenAPI
    url: openapi/heimster-ch-applications-api-openapi.yml
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-telephony-calls-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-objects-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-contacts-response-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-contacts-id-activities-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-viewings-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-patch-api-v1-contacts-id-request-schema.json
- aid: heimster-ch:heimster-ch-contacts-api
  name: Heimster Contacts API
  description: The Contacts API from Heimster — 3 operation(s) for contacts.
  humanURL: https://heimster.ch/developers
  baseURL: https://heimster.ch/api/v1
  tags:
  - Contacts
  properties:
  - type: OpenAPI
    url: openapi/heimster-ch-contacts-api-openapi.yml
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-telephony-calls-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-objects-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-contacts-response-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-contacts-id-activities-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-viewings-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-patch-api-v1-contacts-id-request-schema.json
- aid: heimster-ch:heimster-ch-email-api
  name: Heimster Email API
  description: The Email API from Heimster — 1 operation(s) for email.
  humanURL: https://heimster.ch/developers
  baseURL: https://heimster.ch/api/v1
  tags:
  - Email
  properties:
  - type: OpenAPI
    url: openapi/heimster-ch-email-api-openapi.yml
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-telephony-calls-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-objects-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-contacts-response-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-contacts-id-activities-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-viewings-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-patch-api-v1-contacts-id-request-schema.json
- aid: heimster-ch:heimster-ch-export-api
  name: Heimster Export API
  description: The Export API from Heimster — 1 operation(s) for export.
  humanURL: https://heimster.ch/developers
  baseURL: https://heimster.ch/api/v1
  tags:
  - Export
  properties:
  - type: OpenAPI
    url: openapi/heimster-ch-export-api-openapi.yml
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-telephony-calls-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-objects-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-contacts-response-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-contacts-id-activities-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-viewings-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-patch-api-v1-contacts-id-request-schema.json
- aid: heimster-ch:heimster-ch-follow-ups-api
  name: Heimster Follow Ups API
  description: The Follow Ups API from Heimster — 1 operation(s) for follow ups.
  humanURL: https://heimster.ch/developers
  baseURL: https://heimster.ch/api/v1
  tags:
  - Follow-ups
  tags_raw:
  - Follow Ups
  properties:
  - type: OpenAPI
    url: openapi/heimster-ch-follow-ups-api-openapi.yml
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-telephony-calls-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-objects-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-contacts-response-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-contacts-id-activities-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-viewings-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-patch-api-v1-contacts-id-request-schema.json
- aid: heimster-ch:heimster-ch-interested-parties-api
  name: Heimster Interested Parties API
  description: The Interested Parties API from Heimster — 1 operation(s) for interested parties.
  humanURL: https://heimster.ch/developers
  baseURL: https://heimster.ch/api/v1
  tags:
  - Interested Parties
  properties:
  - type: OpenAPI
    url: openapi/heimster-ch-interested-parties-api-openapi.yml
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-telephony-calls-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-objects-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-contacts-response-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-contacts-id-activities-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-viewings-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-patch-api-v1-contacts-id-request-schema.json
- aid: heimster-ch:heimster-ch-leads-api
  name: Heimster Leads API
  description: The Leads API from Heimster — 1 operation(s) for leads.
  humanURL: https://heimster.ch/developers
  baseURL: https://heimster.ch/api/v1
  tags:
  - Leads
  properties:
  - type: OpenAPI
    url: openapi/heimster-ch-leads-api-openapi.yml
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-telephony-calls-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-objects-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-contacts-response-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-contacts-id-activities-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-viewings-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-patch-api-v1-contacts-id-request-schema.json
- aid: heimster-ch:heimster-ch-listings-api
  name: Heimster Listings API
  description: The Listings API from Heimster — 3 operation(s) for listings.
  humanURL: https://heimster.ch/developers
  baseURL: https://heimster.ch/api/v1
  tags:
  - Listings
  properties:
  - type: OpenAPI
    url: openapi/heimster-ch-listings-api-openapi.yml
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-telephony-calls-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-objects-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-contacts-response-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-contacts-id-activities-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-viewings-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-patch-api-v1-contacts-id-request-schema.json
- aid: heimster-ch:heimster-ch-objects-api
  name: Heimster Objects API
  description: The Objects API from Heimster — 3 operation(s) for objects.
  humanURL: https://heimster.ch/developers
  baseURL: https://heimster.ch/api/v1
  tags:
  - Objects
  properties:
  - type: OpenAPI
    url: openapi/heimster-ch-objects-api-openapi.yml
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-telephony-calls-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-objects-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-contacts-response-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-contacts-id-activities-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-viewings-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-patch-api-v1-contacts-id-request-schema.json
- aid: heimster-ch:heimster-ch-opportunities-api
  name: Heimster Opportunities API
  description: The Opportunities API from Heimster — 1 operation(s) for opportunities.
  humanURL: https://heimster.ch/developers
  baseURL: https://heimster.ch/api/v1
  tags:
  - Opportunities
  properties:
  - type: OpenAPI
    url: openapi/heimster-ch-opportunities-api-openapi.yml
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-telephony-calls-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-objects-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-contacts-response-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-contacts-id-activities-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-viewings-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-patch-api-v1-contacts-id-request-schema.json
- aid: heimster-ch:heimster-ch-projects-api
  name: Heimster Projects API
  description: The Projects API from Heimster — 2 operation(s) for projects.
  humanURL: https://heimster.ch/developers
  baseURL: https://heimster.ch/api/v1
  tags:
  - Project
  tags_raw:
  - Projects
  properties:
  - type: OpenAPI
    url: openapi/heimster-ch-projects-api-openapi.yml
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-telephony-calls-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-objects-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-contacts-response-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-contacts-id-activities-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-viewings-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-patch-api-v1-contacts-id-request-schema.json
- aid: heimster-ch:heimster-ch-tasks-api
  name: Heimster Tasks API
  description: The Tasks API from Heimster — 1 operation(s) for tasks.
  humanURL: https://heimster.ch/developers
  baseURL: https://heimster.ch/api/v1
  tags:
  - Task
  tags_raw:
  - Tasks
  properties:
  - type: OpenAPI
    url: openapi/heimster-ch-tasks-api-openapi.yml
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-telephony-calls-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-objects-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-contacts-response-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-contacts-id-activities-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-viewings-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-patch-api-v1-contacts-id-request-schema.json
- aid: heimster-ch:heimster-ch-telephony-api
  name: Heimster Telephony API
  description: The Telephony API from Heimster — 3 operation(s) for telephony.
  humanURL: https://heimster.ch/developers
  baseURL: https://heimster.ch/api/v1
  tags:
  - Telephony
  properties:
  - type: OpenAPI
    url: openapi/heimster-ch-telephony-api-openapi.yml
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-telephony-calls-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-objects-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-contacts-response-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-contacts-id-activities-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-viewings-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-patch-api-v1-contacts-id-request-schema.json
- aid: heimster-ch:heimster-ch-viewings-api
  name: Heimster Viewings API
  description: The Viewings API from Heimster — 1 operation(s) for viewings.
  humanURL: https://heimster.ch/developers
  baseURL: https://heimster.ch/api/v1
  tags:
  - Viewings
  properties:
  - type: OpenAPI
    url: openapi/heimster-ch-viewings-api-openapi.yml
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-telephony-calls-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-objects-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-contacts-response-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-contacts-id-activities-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-post-api-v1-viewings-request-schema.json
  - type: JSONSchema
    url: json-schema/heimster-ch-patch-api-v1-contacts-id-request-schema.json
x-enrichment:
  date: '2026-11-11'
  status: enriched
  artifacts_added: 29
  pass: modular-v1
  engine: identity=local,contract=local,surfaces=local,docs=local,regulatory=local

Heimster API — frequently asked questions

Does Heimster have an API?

Yes. APIs.io lists 16 APIs from Heimster, including Heimster Analytics API, Heimster Anlageobjekte API and Heimster Applications API, and 13 more.

Is there an OpenAPI specification for the Heimster API?

Yes. APIs.io indexes 16 OpenAPI specifications for Heimster, each linked for download from this page.

How much does the Heimster API cost?

Heimster publishes its prices; its Basis plan is CHF 99 per user per month, excl. VAT as of 2026-11-11. APIs.io lists 3 pricing plans for Heimster, with each plan's price, limits and inclusions under Pricing on this page.

Does Heimster have an MCP server?

Yes. APIs.io lists 1 MCP server for Heimster: Remote MCP server at heimster.ch requiring an API key.

Is the Heimster API ready for AI agents?

Heimster has a Kin Score of 39.0 out of 100 (thin) and an Agent Readiness score of 44.1 (agent-ready), scored by API Evangelist on 2026-11-13.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/heimster-ch"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/heimster-ch/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/heimster-ch/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.