Connect your own system: syncing with your CRM
Sync properties with your own number, read what is missing in a structured way, hide the address and bring enquiries into your own system.
Last updated:
To sync with your CRM, use Athaus für Anbieter with an ath_ key.
Properties with your own number
save_property accepts external_id, the property number of your system.
- The same
external_idalways changes the same property; a new one creates a property of its own, even at an address another property already holds. - Without
external_id, the same street, house number and postcode do not produce a second property; the call names the ID of the existing one (adresse_vergeben). - The number appears in
get_property,search_propertiesand the result ofsave_property. Wherever a tool takesproperty_id, theexternal_idworks too. - If a property already carries another number, the call changes nothing and says so.
The number is per office: two offices may use the same one.
Files
files[] on save_property are appended, never replaced. A file whose content is already on the property is skipped (the content is compared, not the name). The result lists it under files.skipped with already_present and the file_id of the existing one. A sync may therefore send the same files on every pass. To remove a file use delete_item with kind: "file", always with a click.
Change price and publish without a click
Two kinds appear under Settings, Approvals and start on Ask first:
| Kind | On Automatic |
|---|---|
| Publish listing | publish_listing goes online without a click if the check passes and the key carries freigeben. On Off the tool accepts nothing. |
| Change price | A price your key states explicitly in save_property (angebotspreis, price_change_eur, price_change_pct) is on the property at once, with freigeben. Otherwise it waits as a suggestion. |
Prices that Athaus reads from mails or documents always wait for a yes.
When the listing is missing something
publish_listing answers with isError, the code unvollstaendig (_meta["athaus/code"]) and a structuredContent:
{
"property_id": "0f6b9a3e-2c11-4d5e-9a77-4b1d2e3f4a5b",
"check": {
"ready": false,
"photos_missing": true,
"next_question": "What price should the listing show?",
"missing": [
{ "field": "preis", "group": "preis", "question": "What price should the listing show?", "save_field": "fields.angebotspreis" }
]
},
"waiting_for_click": false
}missing[].field is the stable code of the mandatory detail (for example street_address, preis, energie_klasse), group its group (wo, eckdaten, preis, energie, text), save_field says where the value belongs in save_property. photos_missing is true while the property has no photo.
Hide the address in the listing
adresse_zeigen goes in fields of save_property:
| Value | The listing shows |
|---|---|
exakt | Street with house number, postcode and town |
strasse | Street without house number, postcode and town |
ort | Postcode and town only |
The choice applies wherever the listing shows the address, including the OpenImmo export. The map point is rounded to about 100 metres with strasse and about a kilometre with ort. Any connection may show less of the address; only your own ath_ key may show more.
Enquiries into your own system
Enquiries land in Athaus and the office gets a mail. Three ways bring them into your system as well.
Automation with a webhook
Under Automations create one: trigger New enquiry, step Send a call (for technical use). Athaus calls your https address at once (port 443 or 8443, publicly reachable), with POST and a JSON body made of the fields you define. Among others these variables are available:
anfrage.vorname,anfrage.name,anfrage.email,anfrage.telefon: the enquirer (for catalogue enquiries only with a release, see below).anfrage.nachricht,.quelle,.stand,.eingegangen,.link: text, origin, state, time, link in Athaus.anfrage.eigenkapital_vorhanden,.finanzierung_bestaetigt(jaor empty) and the main details.finanzierung,.zeitrahmen,.nutzung,.budget,.haushalt_personen,.beschaeftigung,.haustiere,.wbs,.unterlagen(The seeker).objekt.titel,objekt.adresse,objekt.link: the property.
Every call carries an Idempotency-Key, a retry the same one. If your address does not answer with a success, it shows in the run of the automation.
Polling with since and cursor
With since (ISO 8601), search_inquiries returns only enquiries after it, oldest first. With limit (at most 25) you get one page; if next_cursor is in the result, pass it back unchanged as cursor.
{ "since": "2026-11-10T08:00:00Z", "limit": 25, "cursor": "2026-11-10T09:14:02.118Z|0f6b9a3e-2c11-4d5e-9a77-4b1d2e3f4a5b" }Use the angefragt_am of the last enquiry you processed as the next since. Every 30 to 60 seconds is enough (Limits). Fetch the details with get_inquiry.
The name and contact of a catalogue seeker depend on their release. While it holds, search_inquiries, get_inquiry (kontakt) and the automation carry the full name, email and phone. Without a release or after a revocation the name is shortened ("First N."), kontakt is null, anfrage.email and anfrage.telefon are empty; you can still reply in the thread. Enquiries from portals, from your website and ones the office entered carry their contact details as before. On a revocation, delete what your system already has.
The seeker behind a catalogue enquiry
When an enquiry comes through the catalogue from a seeker with a profile, search_inquiries, get_inquiry and the automation carry the seeker's main details (hauptangaben): the same the office sees in the summary of the enquiry, categories instead of amounts.
| Field | Content |
|---|---|
eigenkapital_vorhanden, finanzierung_bestaetigt | true if the seeker stated it (purchase only), otherwise null. Never an amount, never false. |
hauptangaben.art | kauf (purchase) or miete (rent); decides which fields below can be filled. |
finanzierung | Purchase: cash, mortgage_approved or mortgage_planned. |
zeitrahmen | asap, 3_months, 6_months or flexible (the move-in for a rental). |
nutzung | Purchase: own_use or investment. |
budget | Purchase: passt (fits), knapp (tight) or darunter (below) against the price of the property. Never the amount. |
haushalt_personen, beschaeftigung, haustiere, wbs | Rent: household, employment (employed, self_employed, civil_servant, retired, student, other), pets, housing entitlement certificate (only true). |
unterlagen | How many documents are in the seeker's folder. |
A value is there if the seeker shared it for this enquiry, otherwise null; Athaus infers nothing from other details. The block is absent for enquiries from portals, from your website, ones the office entered and ones without a folder, and after a revocation. It never carries name, email or phone.
Events with your own OAuth client
inquiry.received arrives as a signed message (MCP Events) with IDs; fetch the details with get_inquiry. Subscribing works only over OAuth, so you need an OAuth client of your own, not a key. Flow and signature: Events.
Keep reading
MCP Events: webhooks for enquiries, viewings and suggestions
MCP Events as webhooks. A connected app is notified when an enquiry comes in, a viewing is booked or a suggestion is waiting.
Create an API key and choose its scopes
An API key for the REST API, your own agents and services, with exactly the scopes you give it.
MCP limits: rate and sizes
How much the two MCP servers accept at once, how large a call, a list, a text or a file may be, and what no tool does without a click.
Events
MCP Events as webhooks. A connected app is notified when an enquiry comes in, a viewing is booked or a suggestion is waiting.
Cards in chat
The cards ChatGPT and Claude draw in the chat: a property, listings as a list, the exposé with an enquiry form, enquiries, a search brief and the confirmation.