Developers

Pando API

Connect your own software to a Pando agency: read and create contacts, send leads into the agency's inbox, create and update properties with their photos, publish them to the portals, and read tasks and create tasks and notes. Every request acts for one agency, the one that created the API key.

Base URL
https://www.pando.immo/api/v1
Authentication
Authorization: Bearer pando_sk_...
Format
JSON in, JSON out
Limit
120 requests per minute per key

1. Get a key

  1. Log in to Pando as an owner or admin of the agency.
  2. Go to Instellingen > API and create a key.
  3. Tick only the scopes you need. The key is shown once: store it as a secret, never in a browser or an app.
  4. Lost it, or a colleague left? Revoke it there and create a new one.
  • contacts:readList contacts.
  • contacts:writeCreate and change contacts, e-mail a contact; converting a lead also needs it.
  • properties:readList properties.
  • properties:writeCreate and change properties, add photos and notes, record bids (always pending), draft descriptions with AI (counts on the AI allowance), request missing documents from the seller by mail.
  • publications:readRead per portal where a property is published and which portals have older data.
  • publications:writePublish to portals, take offline and send changes to a live advert.
  • leads:readList leads.
  • leads:writeSend leads, assign them, move them to another stage and convert them into a contact.
  • notes:writeAdd notes to contacts.
  • tasks:readList tasks and get the daily briefing.
  • tasks:writeCreate tasks.
  • visits:readList visits and see when an agent is free.
  • visits:writePlan visits, record their outcome, move them and mail the visitor the confirmation or reminder.

2. Make a request

curl https://www.pando.immo/api/v1/properties?status=active \
  -H "Authorization: Bearer pando_sk_..."

Lists return { "data": [...], "pagination": { "limit", "offset", "total" } }. Page with limit (1 to 200, default 50) and offset. Errors return { "error": "code" } with the HTTP status below.

  • 400invalid_jsonThe body is not valid JSON.
  • 401missing_bearer_tokenNo Authorization: Bearer header.
  • 401invalid_tokenUnknown or revoked key, or the agency is suspended.
  • 403insufficient_scopeThe key lacks the scope; the body names it in "required".
  • 422invalid_payloadThe body does not match; "details" says which field.
  • 429rate_limitedMore than 120 requests in a minute with one key.
  • 500query_failed / create_failedSomething went wrong on our side. Retry later.

One more limit sits in front of the REST endpoints: at most 300 requests per minute from one IP address. Above that, requests from that address are refused for a minute, and that answer is not JSON. A first sync of many listings (each with its photos) should be spread over time.

3. Endpoints

GET/api/v1/contactsscope contacts:read

List contacts

The agency's contacts, newest first, each with its search profile. Filter with type. The fits_* filters keep only buyers and renters still searching whose search profile fits those facts, by the same rule as "Matchende kopers": a fact that breaks a set criterion drops the contact, a fact you leave out never does. Such a list is read completely and then paged.

Query parameters

  • limitintegerdefault 50

    Rows per page.

  • offsetintegerdefault 0

    Rows to skip.

  • typestring

    Only contacts with this role.

    seller · buyer · renter · landlord · syndic · notary · notary_buyer · notary_seller · other

  • fits_transactionstring

    Search profile fits a property for sale or for rent.

    sale · rent

  • fits_property_typestring

    Search profile fits this kind of property.

    apartment · studio · house · terraced_house · semi_detached · detached_villa · mansion · building_land · land · commercial · garage · other

  • fits_postal_codestring

    Search profile fits this 4-digit postcode.

  • fits_pricenumber

    Search profile fits this price in EUR (their maximum is not lower).

  • fits_bedroomsinteger

    Search profile fits this many bedrooms (their minimum is not higher).

Example

curl "https://www.pando.immo/api/v1/contacts?fits_transaction=sale&fits_postal_code=2600&fits_price=400000&fits_bedrooms=3" \
  -H "Authorization: Bearer pando_sk_..."
Response 200 - data: list of 25 fields
  • iduuid

    Pando id of the contact.

  • typestring

    Role of the contact.

    seller · buyer · renter · landlord · syndic · notary · notary_buyer · notary_seller · other

  • first_namestring | null

    First name.

  • last_namestring | null

    Last name.

  • company_namestring | null

    Company name, for a company contact.

  • emailemail | null

    E-mail address.

  • phonestring | null

    Phone number.

  • mobilestring | null

    Mobile number.

  • streetstring | null

    Street and number.

  • postal_codestring | null

    Postal code.

  • citystring | null

    City.

  • languagestring

    Language to address the contact in.

    nl · fr · en

  • sourcestring | null

    Where the contact came from.

  • tagsstring[]

    Free tags.

  • gdpr_consent_atdate-time | null

    When the contact agreed to be contacted about their own request. Never set through the API.

  • marketing_consent_atdate-time | null

    When the contact agreed to receive marketing. Set through the API only with marketing_consent (POST /contacts, PATCH /contacts/{id}).

  • search_transactionstring | null

    Search profile: wants to buy (sale) or rent.

    sale · rent

  • search_property_typesstring[]

    Search profile: kinds of property wanted (empty = any).

  • search_min_bedroomsinteger | null

    Search profile: at least this many bedrooms.

  • search_max_pricenumber | null

    Search profile: highest price in EUR (monthly rent for a renter).

  • search_min_surfaceinteger | null

    Search profile: at least this living area in m².

  • search_postal_codesstring[]

    Search profile: wanted postcodes (empty = anywhere).

  • created_atdate-time

    When the record was created.

  • updated_atdate-time

    When the record last changed.

  • pipeline_stagestring

    The "Fase" of the contact in Pando. Sellers and landlords: new, qualifying, valuation, mandate, for_sale, under_offer, closing, won, lost. Buyers and renters: new, qualifying, searching, viewing, offer, under_offer, closing, won, lost.

    new · qualifying · under_offer · closing · won · lost · valuation · mandate · for_sale · searching · viewing · offer

POST/api/v1/contactsscope contacts:write

Create a contact

Adds a contact to the agency. Marketing consent is only set with `marketing_consent` (e.g. carried over from the previous CRM); without it the contact is not mailed marketing until the agency records a real opt-in. Send your own id as `external_ref` to make re-sending safe; a re-send returns the contact unchanged, also its consent (change that with PATCH /contacts/{id}).

Body (JSON)

Send at least one of first_name, last_name, company_name or email.

  • typestringrequired

    Role of the contact.

    seller · buyer · renter · landlord · syndic · notary · notary_buyer · notary_seller · other

  • first_namestring

    First name.

  • last_namestring

    Last name.

  • company_namestring

    Company name, for a company contact.

  • emailemail

    E-mail address.

  • phonestring

    Phone number.

  • mobilestring

    Mobile number.

  • streetstring

    Street and number.

  • postal_codestring

    Postal code.

  • citystring

    City.

  • languagestringdefault nl

    Language to address the contact in.

    nl · fr · en

  • sourcestringdefault api

    Where the contact came from.

  • notesstring

    Free notes.

  • tagsstring[]

    Free tags.

  • external_refstring | null

    Your own id for this contact. Sending it again returns the same contact (created: false) instead of a second one; 409 external_ref_conflict if that id already belongs to another person.

  • marketing_consentobject

    Marketing consent carried over from another system ("may this contact be mailed? yes/no"). given true sets marketing_consent_at once: refused with 409 contact_opted_out when the contact unsubscribed or its address is on the office's suppression list; a consent that already exists is kept unchanged and answered. given false withdraws only a consent that came from an import or the API; a consent given in Pando itself is kept and answered with 409 consent_captured_in_pando. Never sets or clears an opt-out. Absent = unchanged.

    • givenbooleanrequired

      true = the contact agreed to receive marketing mail; false = withdraw an imported or API consent.

    • atdate-time

      Only with given true: when the contact agreed, as recorded in the other system. Not in the future, not before 1990. Absent = now.

    • sourcestringrequired

      Short name of the system the answer comes from, e.g. zabun: lower-case letters, digits and single dashes. Stored as "<source>_import".

Example

curl -X POST "https://www.pando.immo/api/v1/contacts" \
  -H "Authorization: Bearer pando_sk_..." \
  -H "Content-Type: application/json" \
  -d '{
    "type": "seller",
    "first_name": "An",
    "last_name": "Peeters",
    "email": "an.peeters@example.com",
    "language": "nl"
  }'
Response 201 (200 when it already existed) - created, data: 26 fields
  • iduuid

    Pando id of the contact.

  • typestring

    Role of the contact.

    seller · buyer · renter · landlord · syndic · notary · notary_buyer · notary_seller · other

  • first_namestring | null

    First name.

  • last_namestring | null

    Last name.

  • company_namestring | null

    Company name, for a company contact.

  • emailemail | null

    E-mail address.

  • phonestring | null

    Phone number.

  • mobilestring | null

    Mobile number.

  • streetstring | null

    Street and number.

  • postal_codestring | null

    Postal code.

  • citystring | null

    City.

  • languagestring

    Language to address the contact in.

    nl · fr · en

  • sourcestring | null

    Where the contact came from.

  • tagsstring[]

    Free tags.

  • gdpr_consent_atdate-time | null

    When the contact agreed to be contacted about their own request. Never set through the API.

  • marketing_consent_atdate-time | null

    When the contact agreed to receive marketing. Set through the API only with marketing_consent (POST /contacts, PATCH /contacts/{id}).

  • search_transactionstring | null

    Search profile: wants to buy (sale) or rent.

    sale · rent

  • search_property_typesstring[]

    Search profile: kinds of property wanted (empty = any).

  • search_min_bedroomsinteger | null

    Search profile: at least this many bedrooms.

  • search_max_pricenumber | null

    Search profile: highest price in EUR (monthly rent for a renter).

  • search_min_surfaceinteger | null

    Search profile: at least this living area in m².

  • search_postal_codesstring[]

    Search profile: wanted postcodes (empty = anywhere).

  • created_atdate-time

    When the record was created.

  • updated_atdate-time

    When the record last changed.

  • pipeline_stagestring

    The "Fase" of the contact in Pando. Sellers and landlords: new, qualifying, valuation, mandate, for_sale, under_offer, closing, won, lost. Buyers and renters: new, qualifying, searching, viewing, offer, under_offer, closing, won, lost.

    new · qualifying · under_offer · closing · won · lost · valuation · mandate · for_sale · searching · viewing · offer

  • marketing_consentobject

    The marketing consent as it stands after the call.

    • givenbooleanrequired

      true = the contact may receive marketing mail: a consent is recorded and the contact did not unsubscribe.

    • atdate-time | nullrequired

      When the consent was given; null = none.

    • sourcestring | nullrequired

      Where it came from, e.g. zabun_import; null = given in Pando itself, or no consent.

POST/api/v1/contacts/{id}/notesscope notes:write

Add a note to a contact

Adds a note to a contact of the agency, shown in the contact's history (Historiek) in Pando. Also a history item from another system: `occurred_at` keeps the original moment (the history sorts on it), `kind` labels it (call, mail, visit, sms, portal, note), `property_id` links a property and `agent_id` names the agent. A note never sends mail, makes no task and is no call log. Notes are write-only through the API: they are never read back in a contact list. Send your own id as `external_ref` to make re-sending safe; it is required with `occurred_at`.

Path parameters

  • iduuidrequired

    Pando id of the contact (from GET /contacts or POST /contacts).

Body (JSON)

  • bodystringrequired

    The note text.

  • pinnedbooleandefault false

    Pin the note to the top of the contact's notes.

  • external_refstring | null

    Your own id for the note. Sending it again with the same content returns the same note; 409 external_ref_conflict if it belongs to another note. Required with occurred_at.

  • occurred_atdate-time

    When it happened (ISO 8601 with time zone). Not in the future, not before 1990. Absent = now.

  • kindstring

    What the note is about, shown as a label. Absent = a plain note.

    note · call · mail · visit · sms · portal

  • property_iduuid

    A property of the agency the note is about (from GET /properties).

  • agent_iduuid

    An active agent of the agency shown as author (from GET /agents). Absent = the key's maker. With an agent's own sign-in only that agent.

Example

curl -X POST "https://www.pando.immo/api/v1/contacts/{id}/notes" \
  -H "Authorization: Bearer pando_sk_..." \
  -H "Content-Type: application/json" \
  -d '{
    "body": "Belde terug, wil zaterdag bezoeken.",
    "external_ref": "crm-note-123"
  }'
Response 201 (200 when it already existed) - created, data: 10 fields
  • iduuid

    Pando id of the note.

  • contact_iduuid

    The contact the note is on.

  • bodystring

    The note text.

  • pinnedboolean

    Pinned to the top of the contact's notes.

  • external_refstring | null

    Your own id for the note, if you sent one.

  • property_iduuid | null

    The property the note is about, if any.

  • kindstring | null

    What the note is about (a label in the contact's history); null = a plain note.

    note · call · mail · visit · sms · portal

  • agent_iduuid | null

    The agent shown as author; null when unknown.

  • created_atdate-time

    When it happened: occurred_at when you sent one, else when the note was created. The contact's history sorts on it.

  • updated_atdate-time

    When the record last changed.

GET/api/v1/propertiesscope properties:read

List properties

The agency's properties, newest first. Every filter is optional; together they all apply. A price or bedroom filter leaves out properties where that fact is not filled in. Fees and commission are never part of this API.

Query parameters

  • limitintegerdefault 50

    Rows per page.

  • offsetintegerdefault 0

    Rows to skip.

  • statusstring

    Only properties with this status.

    draft · active · under_offer · sold · rented · withdrawn

  • typestring

    Only this kind of property.

    apartment · studio · house · terraced_house · semi_detached · detached_villa · mansion · building_land · land · commercial · garage · other

  • transaction_typestring

    Only for sale or only for rent.

    sale · rent

  • postal_codestring

    Only this 4-digit postcode.

  • citystring

    Only this city (the whole name, any case).

  • min_pricenumber

    Price at least this, in EUR.

  • max_pricenumber

    Price at most this, in EUR.

  • min_bedroomsinteger

    At least this many bedrooms.

Example

curl "https://www.pando.immo/api/v1/properties?status=active&city=Berchem&max_price=400000&min_bedrooms=3" \
  -H "Authorization: Bearer pando_sk_..."
Response 200 - data: list of 18 fields
  • iduuid

    Pando id of the property.

  • referencestring | null

    The agency's own reference, e.g. CI-2026-004. Pando fills it in.

  • external_refstring | null

    Your own id for this listing, as you sent it. Null for properties made in Pando.

  • typestring

    Kind of property.

    apartment · studio · house · terraced_house · semi_detached · detached_villa · mansion · building_land · land · commercial · garage · other

  • transaction_typestring

    For sale or for rent.

    sale · rent

  • statusstring

    Where the property is in its life cycle.

    draft · active · under_offer · sold · rented · withdrawn

  • streetstring

    Street.

  • numberstring | null

    House number (and box).

  • postal_codestring

    Postal code.

  • citystring

    City.

  • pricenumber | null

    Asking price in EUR, or the monthly rent for a rental.

  • bedroomsinteger | null

    Number of bedrooms.

  • bathroomsinteger | null

    Number of bathrooms.

  • surface_livingnumber | null

    Living area in m².

  • epc_labelstring | null

    EPC label.

    A+ · A · B · C · D · E · F · G

  • featured_image_urlstring | null

    URL of the main photo.

  • created_atdate-time

    When the record was created.

  • updated_atdate-time

    When the record last changed.

GET/api/v1/properties/{id}scope properties:read

Get one property

One property of the agency, with the same fields as the list. Fees and commission are never part of this API.

Path parameters

  • iduuidrequired

    Pando id of the property.

Example

curl "https://www.pando.immo/api/v1/properties/{id}" \
  -H "Authorization: Bearer pando_sk_..."
Response 200 - data: 18 fields
  • iduuid

    Pando id of the property.

  • referencestring | null

    The agency's own reference, e.g. CI-2026-004. Pando fills it in.

  • external_refstring | null

    Your own id for this listing, as you sent it. Null for properties made in Pando.

  • typestring

    Kind of property.

    apartment · studio · house · terraced_house · semi_detached · detached_villa · mansion · building_land · land · commercial · garage · other

  • transaction_typestring

    For sale or for rent.

    sale · rent

  • statusstring

    Where the property is in its life cycle.

    draft · active · under_offer · sold · rented · withdrawn

  • streetstring

    Street.

  • numberstring | null

    House number (and box).

  • postal_codestring

    Postal code.

  • citystring

    City.

  • pricenumber | null

    Asking price in EUR, or the monthly rent for a rental.

  • bedroomsinteger | null

    Number of bedrooms.

  • bathroomsinteger | null

    Number of bathrooms.

  • surface_livingnumber | null

    Living area in m².

  • epc_labelstring | null

    EPC label.

    A+ · A · B · C · D · E · F · G

  • featured_image_urlstring | null

    URL of the main photo.

  • created_atdate-time

    When the record was created.

  • updated_atdate-time

    When the record last changed.

GET/api/v1/leadsscope leads:read

List leads

The agency's Leads inbox, newest first. To poll for new leads (for example from Zapier or Make), pass the time of your last check as `since` and skip ids you already have.

Query parameters

  • limitintegerdefault 50

    Rows per page.

  • offsetintegerdefault 0

    Rows to skip.

  • sincedate-time

    Only leads created at or after this moment (ISO 8601).

  • lead_typestring

    Only sellers or only buyers.

    seller · buyer

Example

curl "https://www.pando.immo/api/v1/leads?since=2026-09-29T08:00:00Z&lead_type=seller" \
  -H "Authorization: Bearer pando_sk_..."
Response 200 - data: list of 24 fields
  • iduuid

    Pando id of the lead.

  • sourcestring

    Where the lead came from.

  • lead_typestring

    seller = someone who wants to sell or rent out; buyer = someone looking to buy or rent.

    seller · buyer

  • statusstring | null

    Stage in the agency's Leads inbox.

    new · contacted · appointment · converted · rejected

  • namestring | null

    Name of the person.

  • emailemail | null

    E-mail address.

  • phonestring | null

    Phone number.

  • intereststring | null

    What the person asked for.

  • property_iduuid | null

    The agency's property this lead is about, when it could be linked.

  • property_addressstring | null

    Address the lead is about.

  • postal_codestring | null

    Postal code.

  • notesstring | null

    Free notes.

  • external_refstring | null

    Your own id for this lead, as you sent it.

  • utm_sourcestring | null

    utm_source sent with the lead.

  • utm_mediumstring | null

    utm_medium sent with the lead.

  • utm_campaignstring | null

    utm_campaign sent with the lead.

  • utm_contentstring | null

    utm_content sent with the lead.

  • utm_termstring | null

    utm_term sent with the lead.

  • landing_pagestring | null

    Path of the page the form was on.

  • contact_iduuid | null

    The contact this lead became, once the agent converted it.

  • convertedboolean

    True once the lead is linked to a contact.

  • received_atdate-time | null

    When the lead arrived.

  • created_atdate-time

    When the record was created.

  • updated_atdate-time

    When the record last changed.

POST/api/v1/leadsscope leads:write

Send a lead

Puts a lead in the agency's Leads inbox (status new), from any source: a website form, Zapier or Make, your own software. Send your own id as `external_ref`: sending the same external_ref again from the same source updates that lead instead of creating a second one. Empty strings count as "not filled in". An invalid e-mail address does not reject the lead: it is dropped and kept in the notes. The utm_* fields and landing_page are recorded once: sending the lead again never changes or clears them (they are only filled when the lead has none yet). Pando sends no mail to the person for a lead from this endpoint, with one exception: when the agency marked the API key "Eigen formulier" (own lead form) and turned on its guide mail for that source, a NEW lead with an e-mail address gets that guide once. A lead created through the MCP server never gets it.

Body (JSON)

Send at least one of name, email or phone.

  • lead_typestringdefault buyer

    seller = wants to sell or rent out; buyer = looking to buy or rent.

    seller · buyer

  • sourcestringdefault api

    Name of your channel, shown to the agent.

  • external_refstring

    Your own id for this lead. Makes re-sending safe.

  • namestring

    Name of the person.

  • emailstring

    E-mail address.

  • phonestring

    Phone number.

  • property_iduuid

    Id of one of the agency's properties (from GET /properties). A property of another agency is never linked; the lead still arrives.

  • property_addressstring

    Address the lead is about. Filled in by Pando when property_id is linked.

  • postal_codestring

    Postal code.

  • intereststring

    What the person asked for.

  • notesstring

    Free notes.

  • utm_sourcestring

    utm_source of the visit that led to this lead (for example google, facebook). Values longer than 200 characters are shortened; a value that is not a string is ignored, never a reason to reject the lead.

  • utm_mediumstring

    utm_medium of that visit (for example cpc, email). Same rules as utm_source.

  • utm_campaignstring

    utm_campaign of that visit. Same rules as utm_source.

  • utm_contentstring

    utm_content of that visit. Same rules as utm_source.

  • utm_termstring

    utm_term of that visit. Same rules as utm_source.

  • landing_pagestring

    Path of the page the form was on, for example /verkopen-antwerpen. A full https URL is accepted; Pando keeps only its path and always drops ?query and #fragment. At most 500 characters.

Example

curl -X POST "https://www.pando.immo/api/v1/leads" \
  -H "Authorization: Bearer pando_sk_..." \
  -H "Content-Type: application/json" \
  -d '{
    "lead_type": "seller",
    "source": "my-website",
    "external_ref": "form-8841",
    "name": "Jan Janssens",
    "email": "jan.janssens@example.com",
    "phone": "+32 470 00 00 00",
    "property_address": "Kerkstraat 12, 9000 Gent",
    "interest": "Wants a valuation",
    "utm_source": "google",
    "utm_medium": "cpc",
    "utm_campaign": "verkopen-antwerpen",
    "landing_page": "/verkopen-antwerpen"
  }'
Response 201: 3 fields
  • okboolean

    Always true on success.

  • iduuid

    Pando id of the lead.

  • createdboolean

    false when an existing lead with the same source and external_ref was updated.

GET/api/v1/tasksscope tasks:read

List tasks

The agency's tasks (a key is office-wide), soonest due first; tasks without a due date come last.

Query parameters

  • limitintegerdefault 50

    Rows per page.

  • offsetintegerdefault 0

    Rows to skip.

  • statusstring

    Only open or only done tasks.

    open · done

  • due_beforedate-time

    Only tasks due before this instant.

Example

curl "https://www.pando.immo/api/v1/tasks?status=open" \
  -H "Authorization: Bearer pando_sk_..."
Response 200 - data: list of 16 fields
  • iduuid

    Pando id of the task.

  • titlestring

    What has to be done.

  • descriptionstring | null

    More detail.

  • due_atdate-time | null

    When it is due.

  • completed_atdate-time | null

    When it was done; null while open.

  • prioritystring | null

    Priority.

    low · normal · high · urgent

  • related_property_iduuid | null

    Linked property.

  • related_contact_iduuid | null

    Linked contact.

  • related_lead_iduuid | null

    Linked lead.

  • originstring | null

    Who made it: null = a person in Pando, api = the API or an AI assistant, other values = a Pando automation.

  • external_refstring | null

    Your own id for the task, if you sent one.

  • created_atdate-time

    When the record was created.

  • updated_atdate-time

    When the record last changed.

  • property_addressstring | null

    Address of the linked property. Needs properties:read, else null.

  • contact_namestring | null

    Name of the linked contact. Needs contacts:read, else null.

  • lead_namestring | null

    Name of the linked lead. Needs leads:read, else null.

POST/api/v1/tasksscope tasks:write

Create a task

Adds a task to the agency, assigned to the person who made the API key. It can be linked to a property, a contact or a lead of the agency. Send your own id as `external_ref` to make re-sending safe.

Body (JSON)

  • titlestringrequired

    What has to be done.

  • descriptionstring | null

    More detail.

  • prioritystringdefault normal

    Priority.

    low · normal · high · urgent

  • due_atdate-time | null

    When it is due (ISO 8601).

  • related_property_iduuid | null

    Id of one of the agency's properties.

  • related_contact_iduuid | null

    Id of one of the agency's contacts.

  • related_lead_iduuid | null

    Id of one of the agency's leads.

  • external_refstring | null

    Your own id for the task. Sending it again returns the same task; 409 if it belongs to another task.

Example

curl -X POST "https://www.pando.immo/api/v1/tasks" \
  -H "Authorization: Bearer pando_sk_..." \
  -H "Content-Type: application/json" \
  -d '{
    "title": "Verkoper terugbellen",
    "priority": "high",
    "external_ref": "crm-task-123"
  }'
Response 201 (200 when it already existed) - created, data: 13 fields
  • iduuid

    Pando id of the task.

  • titlestring

    What has to be done.

  • descriptionstring | null

    More detail.

  • due_atdate-time | null

    When it is due.

  • completed_atdate-time | null

    When it was done; null while open.

  • prioritystring | null

    Priority.

    low · normal · high · urgent

  • related_property_iduuid | null

    Linked property.

  • related_contact_iduuid | null

    Linked contact.

  • related_lead_iduuid | null

    Linked lead.

  • originstring | null

    Who made it: null = a person in Pando, api = the API or an AI assistant, other values = a Pando automation.

  • external_refstring | null

    Your own id for the task, if you sent one.

  • created_atdate-time

    When the record was created.

  • updated_atdate-time

    When the record last changed.

GET/api/v1/visitsscope visits:read

List visits

The agency's visits (a key is office-wide), soonest first. A day (YYYY-MM-DD) in from/to is a Brussels calendar day: from = from its start, to = up to its end. An instant needs Z or an offset.

Query parameters

  • limitintegerdefault 50

    Rows per page.

  • offsetintegerdefault 0

    Rows to skip.

  • fromstring

    Only visits starting on/after this day (YYYY-MM-DD, Brussels) or instant (ISO 8601 with Z or offset).

  • tostring

    Only visits starting on/before this day (YYYY-MM-DD, Brussels, whole day) or instant (ISO 8601 with Z or offset).

  • property_iduuid

    Only visits of this property.

  • contact_iduuid

    Only visits of this visitor.

  • statusstring

    Only visits with this status.

    scheduled · completed · cancelled · no_show

Example

curl "https://www.pando.immo/api/v1/visits?from=2026-10-20&to=2026-10-26&status=scheduled" \
  -H "Authorization: Bearer pando_sk_..."
Response 200 - data: list of 20 fields
  • iduuid

    Pando id of the visit.

  • property_iduuid

    The visited property.

  • contact_iduuid | null

    The visitor (a contact of the office).

  • agent_iduuid | null

    The agent who does the visit.

  • scheduled_atdate-time

    When the visit starts.

  • duration_minutesinteger | null

    Length in minutes.

  • statusstring | null

    scheduled, completed, cancelled or no_show.

    scheduled · completed · cancelled · no_show

  • booked_viastring

    agent = planned by the office (also through the API); self_booked = the buyer booked it online.

    agent · self_booked

  • awaitingstring | null

    A self-booked request still waiting for the agent or the buyer; null otherwise.

    agent · buyer

  • intereststring | null

    The visitor's interest after the visit.

    interested · not_interested

  • decline_reasonstring | null

    Why the visitor dropped out; only with interest not_interested.

    price · location · condition · too_small · financing · bought_elsewhere · situation_changed · just_looking · unresponsive · other · other_offer_accepted

  • feedback_ratinginteger | null

    The visitor's rating, 1 to 5.

  • feedback_notesstring | null

    The visitor's feedback.

  • feedback_visibilitystring

    team = office only; owner = the feedback also appears in the seller report.

    team · owner

  • confirmation_sent_atdate-time | null

    When Pando mailed the visitor a confirmation; null if never.

  • external_refstring | null

    Your own id for the visit, if you sent one.

  • created_atdate-time

    When the record was created.

  • updated_atdate-time

    When the record last changed.

  • property_addressstring | null

    Address of the visited property (street and number, postal code and city). Needs properties:read, else null.

  • visitor_namestring | null

    Name of the visitor (or the company). Needs contacts:read, else null; null without a visitor.

POST/api/v1/visitsscope visits:write

Plan a visit

Plans a visit of one of the agency's properties with status scheduled. Assigned to agent_id, else the person who made the API key (over MCP: the signed-in agent). No e-mail is sent to the visitor, also not when the office has automatic visit confirmations on; the agent can send the confirmation from the agenda in Pando. The visit is stored in the office's Pando agenda and, the same as a visit planned there, Pando copies it into the work calendar the agent doing the visit linked in Pando (Outlook/Microsoft 365, Google or iCloud), not into the calendar of the device or assistant making the call; a calendar that cannot be reached never fails the call. Re-sending the same external_ref adds no second calendar event. There is no overlap check with other visits, the same as planning in the agenda. Send your own id as external_ref to make re-sending safe.

Body (JSON)

  • property_iduuidrequired

    Id of one of the agency's properties.

  • contact_iduuid | null

    The visitor: id of one of the agency's contacts.

  • agent_iduuid | null

    The agent doing the visit: an active agent of the agency.

  • scheduled_atdate-timerequired

    Start, ISO 8601 with Z or an offset (e.g. 2026-10-20T14:00:00+02:00).

  • duration_minutesintegerdefault 30

    Length in minutes.

  • external_refstring | null

    Your own id for the visit. Sending it again returns the same visit; 409 if it belongs to a different visit.

Example

curl -X POST "https://www.pando.immo/api/v1/visits" \
  -H "Authorization: Bearer pando_sk_..." \
  -H "Content-Type: application/json" \
  -d '{
    "property_id": "6f1c2a9e-1b2c-4d5e-8f90-123456789abc",
    "contact_id": "0a7d4c3b-2e1f-4a5b-9c8d-abcdef012345",
    "scheduled_at": "2026-10-20T14:00:00+02:00",
    "duration_minutes": 30,
    "external_ref": "crm-visit-881"
  }'
Response 201 (200 when it already existed) - created, data: 18 fields
  • iduuid

    Pando id of the visit.

  • property_iduuid

    The visited property.

  • contact_iduuid | null

    The visitor (a contact of the office).

  • agent_iduuid | null

    The agent who does the visit.

  • scheduled_atdate-time

    When the visit starts.

  • duration_minutesinteger | null

    Length in minutes.

  • statusstring | null

    scheduled, completed, cancelled or no_show.

    scheduled · completed · cancelled · no_show

  • booked_viastring

    agent = planned by the office (also through the API); self_booked = the buyer booked it online.

    agent · self_booked

  • awaitingstring | null

    A self-booked request still waiting for the agent or the buyer; null otherwise.

    agent · buyer

  • intereststring | null

    The visitor's interest after the visit.

    interested · not_interested

  • decline_reasonstring | null

    Why the visitor dropped out; only with interest not_interested.

    price · location · condition · too_small · financing · bought_elsewhere · situation_changed · just_looking · unresponsive · other · other_offer_accepted

  • feedback_ratinginteger | null

    The visitor's rating, 1 to 5.

  • feedback_notesstring | null

    The visitor's feedback.

  • feedback_visibilitystring

    team = office only; owner = the feedback also appears in the seller report.

    team · owner

  • confirmation_sent_atdate-time | null

    When Pando mailed the visitor a confirmation; null if never.

  • external_refstring | null

    Your own id for the visit, if you sent one.

  • created_atdate-time

    When the record was created.

  • updated_atdate-time

    When the record last changed.

POST/api/v1/visits/{id}/outcomescope visits:write

Record the outcome of a visit

Sets what happened: completed, no_show or cancelled, and optionally the visitor's interest, a decline reason, feedback and a rating. Fields left out stay as they are; null clears them. decline_reason is only stored with interest not_interested (sent now or already stored); any other interest clears a stored reason. feedback_visibility owner shows the feedback in the seller report. A visit the buyer booked online stops waiting for confirmation. No e-mail is sent. The agent's linked calendar follows the same as from the agenda in Pando: a cancelled visit is removed from it.

Path parameters

  • iduuidrequired

    Pando id of the visit (from GET /visits or POST /visits).

Body (JSON)

  • statusstringrequired

    completed, no_show or cancelled.

    completed · cancelled · no_show

  • intereststring | null

    The visitor's interest.

    interested · not_interested

  • decline_reasonstring | null

    Why the visitor dropped out; needs interest not_interested.

    price · location · condition · too_small · financing · bought_elsewhere · situation_changed · just_looking · unresponsive · other

  • feedback_notesstring | null

    The visitor's feedback.

  • feedback_ratinginteger | null

    Rating, 1 to 5.

  • feedback_visibilitystring

    team = office only; owner = also in the seller report.

    team · owner

Example

curl -X POST "https://www.pando.immo/api/v1/visits/{id}/outcome" \
  -H "Authorization: Bearer pando_sk_..." \
  -H "Content-Type: application/json" \
  -d '{
    "status": "completed",
    "interest": "not_interested",
    "decline_reason": "price",
    "feedback_notes": "Vindt de prijs te hoog."
  }'
Response 200 - data: 18 fields
  • iduuid

    Pando id of the visit.

  • property_iduuid

    The visited property.

  • contact_iduuid | null

    The visitor (a contact of the office).

  • agent_iduuid | null

    The agent who does the visit.

  • scheduled_atdate-time

    When the visit starts.

  • duration_minutesinteger | null

    Length in minutes.

  • statusstring | null

    scheduled, completed, cancelled or no_show.

    scheduled · completed · cancelled · no_show

  • booked_viastring

    agent = planned by the office (also through the API); self_booked = the buyer booked it online.

    agent · self_booked

  • awaitingstring | null

    A self-booked request still waiting for the agent or the buyer; null otherwise.

    agent · buyer

  • intereststring | null

    The visitor's interest after the visit.

    interested · not_interested

  • decline_reasonstring | null

    Why the visitor dropped out; only with interest not_interested.

    price · location · condition · too_small · financing · bought_elsewhere · situation_changed · just_looking · unresponsive · other · other_offer_accepted

  • feedback_ratinginteger | null

    The visitor's rating, 1 to 5.

  • feedback_notesstring | null

    The visitor's feedback.

  • feedback_visibilitystring

    team = office only; owner = the feedback also appears in the seller report.

    team · owner

  • confirmation_sent_atdate-time | null

    When Pando mailed the visitor a confirmation; null if never.

  • external_refstring | null

    Your own id for the visit, if you sent one.

  • created_atdate-time

    When the record was created.

  • updated_atdate-time

    When the record last changed.

POST/api/v1/propertiesscope properties:write

Create or update a property

Adds a property to the agency. Send your own id as `external_ref`: sending the same external_ref again UPDATES that property with the fields you send (fields you leave out stay as they are), so re-sending is safe. Answers 201 with created:true for a new property, 200 with created:false for an update. Empty strings count as "not filled in". Unknown fields are refused (422) so a typo never goes unnoticed. The property belongs to the colleague who made the API key. Publishing is a separate call.

Body (JSON)

  • typestringrequired

    Kind of property.

    apartment · studio · house · terraced_house · semi_detached · detached_villa · mansion · building_land · land · commercial · garage · other

  • transaction_typestringrequired

    For sale or for rent.

    sale · rent

  • statusstringdefault draft

    Starting status of a NEW property: draft (not public) or active (for sale or rent). Ignored when the external_ref already exists: change a status with PATCH.

    draft · active

  • streetstringrequired

    Street.

  • postal_codestringrequired

    Postal code.

  • citystringrequired

    City.

  • external_refstring | null

    Your own id for this listing. Sending a property with an external_ref this agency already has UPDATES that property instead of creating a second one.

  • numberstring | null

    House number. Put a box number in `bus`, not here.

  • busstring | null

    Box number (bus / boîte).

  • latitudenumber | null

    WGS84 latitude. Several portals need coordinates.

  • longitudenumber | null

    WGS84 longitude.

  • pricenumber | null

    Asking price in EUR, or the monthly rent for a rental.

  • price_on_requestboolean

    Hide the price where a portal allows it. The price itself is still sent.

  • hide_addressboolean

    Hide the street and number where a portal allows it.

  • sale_methodstring

    How it is sold. With online or public_auction, `price` is the starting price. Ignored for a rental.

    private · online · public_auction

  • titlestring | null

    Short advert title.

  • description_nlstring | null

    Advert text in Dutch. Plain text with an optional light markup: blank line = paragraph, lines starting with "- " = list, **bold**, _italic_ (within one line). Never HTML; Pando sends clean text or the allowed HTML per portal.

  • description_frstring | null

    Advert text in French. Plain text with an optional light markup: blank line = paragraph, lines starting with "- " = list, **bold**, _italic_ (within one line). Never HTML; Pando sends clean text or the allowed HTML per portal.

  • description_enstring | null

    Advert text in English. Plain text with an optional light markup: blank line = paragraph, lines starting with "- " = list, **bold**, _italic_ (within one line). Never HTML; Pando sends clean text or the allowed HTML per portal.

  • surface_livinginteger | null

    Living area in m².

  • surface_plotinteger | null

    Plot area in m².

  • garden_surfacenumber | null

    Garden area in m².

  • terrace_surfacenumber | null

    Terrace area in m².

  • bedroomsinteger | null

    Number of bedrooms.

  • bathroomsinteger | null

    Number of bathrooms.

  • toilet_countinteger | null

    Number of toilets.

  • parkinginteger | null

    Number of parking spaces.

  • floorinteger | null

    Floor of an apartment (0 = ground floor). Immoweb needs it for an apartment.

  • floor_countinteger | null

    Number of floors of the building.

  • facade_countinteger | null

    Number of facades (2, 3 or 4).

  • construction_yearinteger | null

    Year of construction.

  • building_conditionstring | null

    State of the building.

    new · as_new · renovated · good · to_refresh · to_renovate

  • epc_labelstring | null

    EPC label.

    A+ · A · B · C · D · E · F · G

  • epc_valueinteger | null

    EPC score in kWh/m² per year.

  • epc_codestring | null

    EPC certificate number.

  • available_from_typestring | null

    When it is free: immediately (onmiddellijk), at the deed (bij_akte), to be agreed (overeen_te_komen) or on a date (specifieke_datum).

    onmiddellijk · bij_akte · overeen_te_komen · specifieke_datum

  • available_from_datedate | null

    The date, with available_from_type specifieke_datum (YYYY-MM-DD).

  • virtual_tour_urluri | null

    https link to a virtual tour (Matterport and the like).

  • video_urluri | null

    https link to a YouTube or Vimeo video.

Example

curl -X POST "https://www.pando.immo/api/v1/properties" \
  -H "Authorization: Bearer pando_sk_..." \
  -H "Content-Type: application/json" \
  -d '{
    "external_ref": "zwv-10482",
    "type": "house",
    "transaction_type": "sale",
    "status": "active",
    "street": "Kerkstraat",
    "number": "12",
    "postal_code": "8400",
    "city": "Oostende",
    "latitude": 51.2273,
    "longitude": 2.9199,
    "price": 349000,
    "bedrooms": 3,
    "surface_living": 165,
    "epc_label": "C",
    "description_nl": "Instapklare gezinswoning met tuin, vlak bij het centrum."
  }'
Response 201 (200 when it already existed) - created, data: 18 fields
  • iduuid

    Pando id of the property.

  • referencestring | null

    The agency's own reference, e.g. CI-2026-004. Pando fills it in.

  • external_refstring | null

    Your own id for this listing, as you sent it. Null for properties made in Pando.

  • typestring

    Kind of property.

    apartment · studio · house · terraced_house · semi_detached · detached_villa · mansion · building_land · land · commercial · garage · other

  • transaction_typestring

    For sale or for rent.

    sale · rent

  • statusstring

    Where the property is in its life cycle.

    draft · active · under_offer · sold · rented · withdrawn

  • streetstring

    Street.

  • numberstring | null

    House number (and box).

  • postal_codestring

    Postal code.

  • citystring

    City.

  • pricenumber | null

    Asking price in EUR, or the monthly rent for a rental.

  • bedroomsinteger | null

    Number of bedrooms.

  • bathroomsinteger | null

    Number of bathrooms.

  • surface_livingnumber | null

    Living area in m².

  • epc_labelstring | null

    EPC label.

    A+ · A · B · C · D · E · F · G

  • featured_image_urlstring | null

    URL of the main photo.

  • created_atdate-time

    When the record was created.

  • updated_atdate-time

    When the record last changed.

PATCH/api/v1/properties/{id}scope properties:write

Change a property

Changes only the fields you send. null clears a field. A status change works as in Pando: sold or rented records the sale date and tells the portals the property is no longer available; draft or withdrawn takes it offline on the portals it is on. Other changes are NOT sent to the portals on their own: call publish again to update the adverts.

Path parameters

  • iduuidrequired

    Pando id of the property (from POST /properties or GET /properties).

Body (JSON)

Send at least one field.

  • typestring

    Kind of property.

    apartment · studio · house · terraced_house · semi_detached · detached_villa · mansion · building_land · land · commercial · garage · other

  • transaction_typestring

    For sale or for rent.

    sale · rent

  • statusstring

    New status. sold or rented records the sale date and tells the portals it is no longer available; draft or withdrawn takes it offline on the portals it is on.

    draft · active · under_offer · sold · rented · withdrawn

  • streetstring

    Street.

  • postal_codestring

    Postal code.

  • citystring

    City.

  • external_refstring | null

    Your own id for this listing. Sending a property with an external_ref this agency already has UPDATES that property instead of creating a second one.

  • numberstring | null

    House number. Put a box number in `bus`, not here.

  • busstring | null

    Box number (bus / boîte).

  • latitudenumber | null

    WGS84 latitude. Several portals need coordinates.

  • longitudenumber | null

    WGS84 longitude.

  • pricenumber | null

    Asking price in EUR, or the monthly rent for a rental.

  • price_on_requestboolean

    Hide the price where a portal allows it. The price itself is still sent.

  • hide_addressboolean

    Hide the street and number where a portal allows it.

  • sale_methodstring

    How it is sold. With online or public_auction, `price` is the starting price. Ignored for a rental.

    private · online · public_auction

  • titlestring | null

    Short advert title.

  • description_nlstring | null

    Advert text in Dutch. Plain text with an optional light markup: blank line = paragraph, lines starting with "- " = list, **bold**, _italic_ (within one line). Never HTML; Pando sends clean text or the allowed HTML per portal.

  • description_frstring | null

    Advert text in French. Plain text with an optional light markup: blank line = paragraph, lines starting with "- " = list, **bold**, _italic_ (within one line). Never HTML; Pando sends clean text or the allowed HTML per portal.

  • description_enstring | null

    Advert text in English. Plain text with an optional light markup: blank line = paragraph, lines starting with "- " = list, **bold**, _italic_ (within one line). Never HTML; Pando sends clean text or the allowed HTML per portal.

  • surface_livinginteger | null

    Living area in m².

  • surface_plotinteger | null

    Plot area in m².

  • garden_surfacenumber | null

    Garden area in m².

  • terrace_surfacenumber | null

    Terrace area in m².

  • bedroomsinteger | null

    Number of bedrooms.

  • bathroomsinteger | null

    Number of bathrooms.

  • toilet_countinteger | null

    Number of toilets.

  • parkinginteger | null

    Number of parking spaces.

  • floorinteger | null

    Floor of an apartment (0 = ground floor). Immoweb needs it for an apartment.

  • floor_countinteger | null

    Number of floors of the building.

  • facade_countinteger | null

    Number of facades (2, 3 or 4).

  • construction_yearinteger | null

    Year of construction.

  • building_conditionstring | null

    State of the building.

    new · as_new · renovated · good · to_refresh · to_renovate

  • epc_labelstring | null

    EPC label.

    A+ · A · B · C · D · E · F · G

  • epc_valueinteger | null

    EPC score in kWh/m² per year.

  • epc_codestring | null

    EPC certificate number.

  • available_from_typestring | null

    When it is free: immediately (onmiddellijk), at the deed (bij_akte), to be agreed (overeen_te_komen) or on a date (specifieke_datum).

    onmiddellijk · bij_akte · overeen_te_komen · specifieke_datum

  • available_from_datedate | null

    The date, with available_from_type specifieke_datum (YYYY-MM-DD).

  • virtual_tour_urluri | null

    https link to a virtual tour (Matterport and the like).

  • video_urluri | null

    https link to a YouTube or Vimeo video.

Example

curl -X PATCH "https://www.pando.immo/api/v1/properties/{id}" \
  -H "Authorization: Bearer pando_sk_..." \
  -H "Content-Type: application/json" \
  -d '{
    "price": 339000,
    "status": "under_offer"
  }'
Response 200 - data: 18 fields
  • iduuid

    Pando id of the property.

  • referencestring | null

    The agency's own reference, e.g. CI-2026-004. Pando fills it in.

  • external_refstring | null

    Your own id for this listing, as you sent it. Null for properties made in Pando.

  • typestring

    Kind of property.

    apartment · studio · house · terraced_house · semi_detached · detached_villa · mansion · building_land · land · commercial · garage · other

  • transaction_typestring

    For sale or for rent.

    sale · rent

  • statusstring

    Where the property is in its life cycle.

    draft · active · under_offer · sold · rented · withdrawn

  • streetstring

    Street.

  • numberstring | null

    House number (and box).

  • postal_codestring

    Postal code.

  • citystring

    City.

  • pricenumber | null

    Asking price in EUR, or the monthly rent for a rental.

  • bedroomsinteger | null

    Number of bedrooms.

  • bathroomsinteger | null

    Number of bathrooms.

  • surface_livingnumber | null

    Living area in m².

  • epc_labelstring | null

    EPC label.

    A+ · A · B · C · D · E · F · G

  • featured_image_urlstring | null

    URL of the main photo.

  • created_atdate-time

    When the record was created.

  • updated_atdate-time

    When the record last changed.

POST/api/v1/properties/{id}/photosscope properties:write

Add a photo by URL

Pando downloads the photo, keeps its own copy and adds it at the end of the gallery. The URL must be https, on a public address, and answer directly (no redirects) with a JPEG, PNG or WebP of at most 12 MB; the type is checked on the file itself. The first photo becomes the cover, or send featured:true. Sending the same url again for the same property returns the existing photo (200, created:false). At most 60 photos per property.

Path parameters

  • iduuidrequired

    Pando id of the property (from POST /properties or GET /properties).

Body (JSON)

  • urlurirequired

    https URL of the photo.

  • captionstring | null

    Caption.

  • featuredboolean

    Make this the cover photo.

Example

curl -X POST "https://www.pando.immo/api/v1/properties/{id}/photos" \
  -H "Authorization: Bearer pando_sk_..." \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://images.example.com/listings/10482/front.jpg"
  }'
Response 201 (200 when it already existed) - created, data: 7 fields
  • iduuid

    Pando id of the photo.

  • urluri

    Pando's own copy of the photo. Public and stable.

  • source_urluri | null

    The URL you sent.

  • captionstring | null

    Caption.

  • order_indexinteger | null

    Position in the gallery, 0 first.

  • is_featuredboolean | null

    True for the cover photo.

  • created_atdate-time | null

    When the photo was added.

POST/api/v1/properties/{id}/publishscope publications:write

Publish to portals

Publishes the property to the portals you list, through the agency's own portal accounts. One result per portal. A portal refuses up front when the listing misses something it needs (`error`, nothing sent), also in the sandbox. A portal the agency has NOT connected is simulated: nothing is sent and the result says simulated:true. That is the sandbox: build and test against it with no risk. Pull portals (immomaps, luxevastgoed, myfuturehome, tweedehands) must be activated by the agency first. Going live on a portal needs the agency's own contract with that portal. Publishing again updates the advert.

Path parameters

  • iduuidrequired

    Pando id of the property (from POST /properties or GET /properties).

Body (JSON)

  • portalsstring[]required

    One or more of: immoweb, immovlan, immoscoop, spotto, immomaps, luxevastgoed, myfuturehome, tweedehands.

Example

curl -X POST "https://www.pando.immo/api/v1/properties/{id}/publish" \
  -H "Authorization: Bearer pando_sk_..." \
  -H "Content-Type: application/json" \
  -d '{
    "portals": [
      "immoweb",
      "immovlan"
    ]
  }'
Response 200 - data: list of 10 fields
  • portalstring

    The portal.

    immoweb · immovlan · immoscoop · spotto · immomaps · luxevastgoed · myfuturehome · tweedehands

  • acceptedboolean

    True when the publication started. False when it was refused before anything was sent; `error` says why.

  • errorstring | null

    Why it was refused: portal_not_connected (a pull portal the agency has not activated), a portal rule such as missing_price, missing_description, missing_coordinates, immoweb_missing_floor or immoscoop_missing_house_number, or start_failed.

  • statusstring | null

    Where the publication stands.

    pending · published · failed · unpublished

  • simulatedboolean | null

    True when the agency has not connected this portal: nothing was sent. This is the sandbox.

  • external_idstring | null

    The portal's own id for the advert, or a SIM id for a simulated publication.

  • portal_urlstring | null

    Link to the live advert, when the portal gives one. Never for a simulated publication or a pull portal.

  • published_atdate-time | null

    When the last publication succeeded.

  • unpublished_atdate-time | null

    When it was taken offline.

  • error_messagestring | null

    Why the last attempt failed (a code). On a published Immovlan row, `immovlan_unconfirmed` means Immovlan accepted the upload but had still not confirmed the advert 24 hours later (no portal_url).

POST/api/v1/properties/{id}/unpublishscope publications:write

Take offline on one portal

Takes the property offline on one portal. It stays in Pando and on the other portals; publishing again brings the same advert back. A simulated publication is just marked offline. Some portals accept the request and finish it later: then pending is true.

Path parameters

  • iduuidrequired

    Pando id of the property (from POST /properties or GET /properties).

Body (JSON)

  • portalstringrequired

    The portal.

    immoweb · immovlan · immoscoop · spotto · immomaps · luxevastgoed · myfuturehome · tweedehands

Example

curl -X POST "https://www.pando.immo/api/v1/properties/{id}/unpublish" \
  -H "Authorization: Bearer pando_sk_..." \
  -H "Content-Type: application/json" \
  -d '{
    "portal": "immoweb"
  }'
Response 200 - data: 9 fields
  • portalstring

    The portal.

    immoweb · immovlan · immoscoop · spotto · immomaps · luxevastgoed · myfuturehome · tweedehands

  • statusstring | null

    Where the publication stands.

    pending · published · failed · unpublished

  • simulatedboolean | null

    True when the agency has not connected this portal: nothing was sent. This is the sandbox.

  • external_idstring | null

    The portal's own id for the advert, or a SIM id for a simulated publication.

  • portal_urlstring | null

    Link to the live advert, when the portal gives one. Never for a simulated publication or a pull portal.

  • published_atdate-time | null

    When the last publication succeeded.

  • unpublished_atdate-time | null

    When it was taken offline.

  • error_messagestring | null

    Why the last attempt failed (a code). On a published Immovlan row, `immovlan_unconfirmed` means Immovlan accepted the upload but had still not confirmed the advert 24 hours later (no portal_url).

  • pendingboolean

    True when the portal accepted the request but finishes it later (Immovlan, Spotto, sometimes Immoweb).

GET/api/v1/properties/{id}/publicationsscope publications:read

Publication status

Per portal where the property stands, whether it was only simulated, and the link to the advert when the portal gave one.

Path parameters

  • iduuidrequired

    Pando id of the property (from POST /properties or GET /properties).

Example

curl "https://www.pando.immo/api/v1/properties/{id}/publications" \
  -H "Authorization: Bearer pando_sk_..."
Response 200 - data: list of 8 fields
  • portalstring

    The portal.

    immoweb · immovlan · immoscoop · spotto · immomaps · luxevastgoed · myfuturehome · tweedehands

  • statusstring | null

    Where the publication stands.

    pending · published · failed · unpublished

  • simulatedboolean | null

    True when the agency has not connected this portal: nothing was sent. This is the sandbox.

  • external_idstring | null

    The portal's own id for the advert, or a SIM id for a simulated publication.

  • portal_urlstring | null

    Link to the live advert, when the portal gives one. Never for a simulated publication or a pull portal.

  • published_atdate-time | null

    When the last publication succeeded.

  • unpublished_atdate-time | null

    When it was taken offline.

  • error_messagestring | null

    Why the last attempt failed (a code). On a published Immovlan row, `immovlan_unconfirmed` means Immovlan accepted the upload but had still not confirmed the advert 24 hours later (no portal_url).

GET/api/v1/briefingscope tasks:read

What needs attention today

At most 10 items for one agent, ranked: decisions first, like the "Beslissen" block of "Actie nodig" in Pando (new leads nobody contacted yet, an overdue legal client check), then overdue tasks, overdue dated 'Terug contacteren' and visits without a recorded outcome, then today's visits, then today's tasks; ties by created_at. Each item has a reason in plain words. Days are Brussels calendar days. The agent is the one who made the API key (over MCP: the signed-in agent); it gets its own items plus the unassigned ones. A key whose maker is no longer an active agent is office-wide. Dossier deadlines count like "Actie nodig" in Pando: overdue ones rank with the overdue work, the rest (up to 14 days ahead) after today's tasks, then certificates that expired or expire within 30 days, then per property the seller documents still to request. For an agent these follow the property's assigned agent (own plus unassigned). Tasks need tasks:read; leads appear only with leads:read, visits only with contacts:read and properties:read, dossier deadlines, certificates and seller documents only with properties:read. Never contains amounts or commission. `more` is true when more items qualify than are returned.

Example

curl "https://www.pando.immo/api/v1/briefing" \
  -H "Authorization: Bearer pando_sk_..."
Response 200 - data: list of 13 fields
  • kindstring

    What kind of item this is.

    task_overdue · recontact_overdue · visit_no_outcome · step_overdue · lead_new · visit_today · recontact_today · task_today · step_due · certificate_expiring · seller_documents_missing

  • titlestring

    Short title: the task title, the visited property, or the lead's name.

  • whystring

    Why it needs attention, in plain words (e.g. "Task overdue by 3 days").

  • due_atdate-time

    When it was or is due (task due moment, visit time). Left out for a lead.

  • due_datedate

    The Brussels calendar day of due_at. Left out when empty.

  • task_iduuid

    The task, for a task item. Left out when empty.

  • lead_iduuid

    The lead (also a task's linked lead). Left out when empty.

  • contact_iduuid

    The linked contact. Left out when empty.

  • property_iduuid

    The linked property. Left out when empty.

  • visit_iduuid

    The visit, for a visit item. Left out when empty.

  • dossier_step_iduuid

    The dossier step, for a dossier deadline item. Left out when empty.

  • document_iduuid

    The document: the certificate, or the one missing seller document (left out when several are missing).

  • created_atdate-time

    When the record was created (a lead: when it arrived). Left out for dossier and document items.

POST/api/v1/tasks/{id}scope tasks:write

Tick off or postpone a task

Marks a task of the agency done (completed true) or open again (completed false), and/or moves it to tomorrow or next week at its own time of day (Brussels; 09:00 when it had none). The same rules as the Taken screen in Pando: an agent who may only edit their own records can only change their own tasks, and a follow-up task keeps the contact's follow-up date in step.

Path parameters

  • iduuidrequired

    Pando id of the task (from GET /tasks or the briefing).

Body (JSON)

  • completedboolean

    true = done, false = open again.

  • postponestring

    Move the due date to tomorrow or one week later.

    tomorrow · next_week

Example

curl -X POST "https://www.pando.immo/api/v1/tasks/{id}" \
  -H "Authorization: Bearer pando_sk_..." \
  -H "Content-Type: application/json" \
  -d '{
    "completed": true
  }'
Response 200 - data: 13 fields
  • iduuid

    Pando id of the task.

  • titlestring

    What has to be done.

  • descriptionstring | null

    More detail.

  • due_atdate-time | null

    When it is due.

  • completed_atdate-time | null

    When it was done; null while open.

  • prioritystring | null

    Priority.

    low · normal · high · urgent

  • related_property_iduuid | null

    Linked property.

  • related_contact_iduuid | null

    Linked contact.

  • related_lead_iduuid | null

    Linked lead.

  • originstring | null

    Who made it: null = a person in Pando, api = the API or an AI assistant, other values = a Pando automation.

  • external_refstring | null

    Your own id for the task, if you sent one.

  • created_atdate-time

    When the record was created.

  • updated_atdate-time

    When the record last changed.

POST/api/v1/contacts/{id}/activitiesscope notes:write

Log a call or conversation with a contact

Logs a contact moment on a contact of the agency: called, no_answer, voicemail, conversation or wrong_number, with an optional note and property. The same entry as the one-click log on a contact in Pando; it shows in the contact's history. The author is the agent who made the API key (over MCP: the signed-in agent).

Path parameters

  • iduuidrequired

    Pando id of the contact (from GET /contacts or GET /search).

Body (JSON)

  • kindstringrequired

    What happened.

    called · no_answer · voicemail · conversation · wrong_number

  • notestring | null

    A short note.

  • property_iduuid | null

    The property it was about (one of the agency's).

Example

curl -X POST "https://www.pando.immo/api/v1/contacts/{id}/activities" \
  -H "Authorization: Bearer pando_sk_..." \
  -H "Content-Type: application/json" \
  -d '{
    "kind": "called",
    "note": "Wil donderdag langskomen"
  }'
Response 201 (200 when it already existed) - created, data: 6 fields
  • iduuid

    Pando id of the log entry.

  • contact_iduuid

    The contact.

  • property_iduuid | null

    The property it was about, if any.

  • kindstring

    called, no_answer, voicemail, conversation or wrong_number.

    called · no_answer · voicemail · conversation · wrong_number

  • notestring | null

    The note, if any.

  • created_atdate-time

    When it was logged.

GET/api/v1/offersscope properties:read

List offers

The agency's offers (biedingen), newest first, with the bid amount, the property address and the bidder's name. Never internal notes.

Query parameters

  • limitintegerdefault 50

    Rows per page.

  • offsetintegerdefault 0

    Rows to skip.

  • statusstring

    Only offers with this status; pending = waiting for a decision.

    pending · accepted · rejected · countered · withdrawn

  • property_iduuid

    Only offers on this property.

Example

curl "https://www.pando.immo/api/v1/offers?status=pending" \
  -H "Authorization: Bearer pando_sk_..."
Response 200 - data: list of 12 fields
  • iduuid

    Pando id of the offer.

  • property_iduuid

    The property the offer is on.

  • contact_iduuid

    The bidder (a contact of the office).

  • amountnumber

    The bid in EUR.

  • statusstring | null

    pending = waiting for the seller's decision.

    pending · accepted · rejected · countered · withdrawn

  • valid_untildate | null

    Until when the bid stands.

  • conditionsstring | null

    Conditions of the bid (e.g. financing).

  • decline_reasonstring | null

    Why it was declined, when rejected or withdrawn.

  • created_atdate-time

    When the record was created.

  • updated_atdate-time

    When the record last changed.

  • property_addressstring | null

    Address of the property.

  • bidder_namestring | null

    Name of the bidder. Needs contacts:read, else null.

GET/api/v1/resultsscope properties:read

Results per agent

Per agent: leads, visits, offers, mandates and sales this month, quarter or year, days on market, achieved % of the asking price and the agent's own goals. The same numbers as "Per makelaar" on Resultaten in Pando. An owner or admin gets every agent, an agent only their own row. Never revenue or fees. The asking agent is the signed-in agent, or with an API key the agent who made it.

Query parameters

  • periodstringdefault month

    The period, up to now (Brussels).

    month · quarter · year

Example

curl "https://www.pando.immo/api/v1/results?period=month" \
  -H "Authorization: Bearer pando_sk_..."
Response 200 - data: list of 13 fields
  • agent_iduuid | null

    The agent; null = not assigned to anyone.

  • agent_namestring

    The agent's name.

  • leadsinteger

    Leads received in the period.

  • visitsinteger

    Visits done in the period.

  • offersinteger

    Offers received in the period.

  • mandatesinteger

    Mandates signed in the period.

  • salesinteger

    Properties sold in the period.

  • avg_days_on_marketnumber | null

    Average days from first publication to sale.

  • achieved_pctnumber | null

    Accepted offer as % of the asking price, on average.

  • goal_leadsinteger | null

    The agent's own goal for the period, if set.

  • goal_visitsinteger | null

    The agent's own goal for the period, if set.

  • goal_mandatesinteger | null

    The agent's own goal for the period, if set.

  • goal_salesinteger | null

    The agent's own goal for the period, if set.

GET/api/v1/properties/{id}/buyersscope contacts:read

Matching buyers for a property

The buyers or renters of the agency whose search profile fits the property, best first (at most 10), and how many still search. The same match as "Matchende kopers" in Pando; closed searches (won, lost) are left out.

Path parameters

  • iduuidrequired

    Pando id of the property.

Example

curl "https://www.pando.immo/api/v1/properties/{id}/buyers" \
  -H "Authorization: Bearer pando_sk_..."
Response 200 - data: list of 5 fields
  • contact_iduuid

    The buyer or renter.

  • namestring

    Their name.

  • scorenumber

    How well the search profile fits, higher is better: the number of set search criteria (= the length of reasons).

  • reasonsstring[]

    Why they match, one code per search criterion the profile set, as "<criterion>:<fit>": criterion transaction, type, price, bedrooms, surface or postal; fit = the property meets it, unknown = the property has no value for it yet (never a miss). A criterion left empty in the profile gives no code.

  • stagestring

    Where they are in the pipeline.

GET/api/v1/agentsscope contacts:read

List the office's agents

The agency's active agents with their name, role, which one is you, and the calendars each linked in Pando (where planned visits appear), to find the id for assigning a lead or planning a visit.

Example

curl "https://www.pando.immo/api/v1/agents" \
  -H "Authorization: Bearer pando_sk_..."
Response 200 - data: list of 5 fields
  • iduuid

    Pando id of the agent.

  • namestring

    The agent's name.

  • rolestring

    owner, admin or agent.

    owner · admin · agent

  • is_youboolean

    True for the signed-in agent (with an API key: the agent who made the key).

  • linked_calendarsstring[]

    Calendars (microsoft, google, icloud) the agent linked in Pando; visits of this agent planned in Pando or with plan_visit are written into them. Empty = no calendar linked.

POST/api/v1/leads/{id}scope leads:write

Assign a lead or move it to another stage

Hands a lead of the agency to an active agent (or to nobody with null) and/or moves it to another stage: new, rejected, or one of the office's middle stages (contacted and appointment, or the office's own stages by id). The same rules as the Leads inbox in Pando. Converting a lead into a contact is done in Pando.

Path parameters

  • iduuidrequired

    Pando id of the lead (from GET /leads or GET /search).

Body (JSON)

  • assigned_touuid | null

    Id of an active agent (GET /agents); null = nobody.

  • stagestring

    new, contacted, appointment, rejected, or the id of one of the office's own stages.

Example

curl -X POST "https://www.pando.immo/api/v1/leads/{id}" \
  -H "Authorization: Bearer pando_sk_..." \
  -H "Content-Type: application/json" \
  -d '{
    "stage": "contacted"
  }'
Response 200 - data: 5 fields
  • iduuid

    Pando id of the lead.

  • statusstring

    new, contacted, appointment, converted or rejected.

  • custom_stage_iduuid | null

    The office's own stage, if it uses custom stages.

  • assigned_touuid | null

    The agent who owns the lead; null = nobody.

  • updated_atdate-time

    When the lead last changed.

GET/api/v1/properties/{id}/dossierscope properties:read

Dossier progress of a property

The steps of the property's dossier (Voortgang in Pando) in the office's own order, each with how Pando shows it and its deadline day, plus the step count and whether the dossier is closed.

Path parameters

  • iduuidrequired

    Pando id of the property.

Example

curl "https://www.pando.immo/api/v1/properties/{id}/dossier" \
  -H "Authorization: Bearer pando_sk_..."
Response 200 - data: list of 6 fields
  • keystring

    The step's key.

  • labelstring

    The step as the office calls it.

  • viewstring

    How Pando shows it: done, not applicable, open, optional (closed dossier) or the legal client check still open.

    done · nvt · open · optional · legal_open

  • statestring

    The stored state.

    te_doen · bezig · wacht_op · klaar · nvt

  • waiting_forstring | null

    Who the step waits for, when state is wacht_op.

  • due_datedate | null

    Deadline day (Brussels), if set.

POST/api/v1/contacts/{id}/email/previewscope contacts:write

Preview an e-mail to a contact

Step 1 of e-mailing a contact: the exact mail Pando would send (address, subject, the full text with the office's house style and the agent's signature) and a confirm_token. Sends and stores nothing.

Path parameters

  • iduuidrequired

    Pando id of the contact (from GET /search or GET /contacts).

Body (JSON)

  • subjectstringrequired

    The subject.

  • messagestringrequired

    The message, plain text; blank lines start a new paragraph.

Example

curl -X POST "https://www.pando.immo/api/v1/contacts/{id}/email/preview" \
  -H "Authorization: Bearer pando_sk_..." \
  -H "Content-Type: application/json" \
  -d '{
    "subject": "Uw bezoek van morgen",
    "message": "Beste Jonas,\n\nKunnen we morgen om 17 uur afspreken in plaats van 16 uur?"
  }'
Response 200 - data: 7 fields
  • contact_iduuid

    The contact the mail goes to.

  • toemail

    The address the mail goes to.

  • to_namestring

    The contact's name.

  • languagestring

    The language of the mail's frame (greeting line of the house style).

    nl · fr · en

  • subjectstring

    The subject line.

  • textstring

    The mail as plain text, exactly as it will be sent (house style, signature).

  • confirm_tokenstring

    Send it to POST /contacts/{id}/email with the same subject and message. Valid as long as the mail would stay the same.

POST/api/v1/contacts/{id}/emailscope contacts:write

E-mail a contact

Step 2: sends the previewed mail from the agent to a contact of the agency, through the office's own mail setup (its own mailbox when connected, else Pando's sender), in the office's house style with the agent's signature; replies go to the agent. Send the same subject and message as the preview plus its confirm_token: when the mail would differ now, the answer is 409 preview_changed with the new preview and nothing is sent. An address set or changed through the API less than 24 hours ago is refused (409 recipient_recently_set_via_api). The mail is recorded as a note on the contact. Send your own id as external_ref: the same ref again answers the earlier send instead of mailing twice.

Path parameters

  • iduuidrequired

    Pando id of the contact (from GET /search or GET /contacts).

Body (JSON)

  • subjectstringrequired

    The subject.

  • messagestringrequired

    The message, plain text; blank lines start a new paragraph.

  • confirm_tokenstringrequired

    The confirm_token of POST /contacts/{id}/email/preview.

  • external_refstring | null

    Your own id for this mail, for safe retries.

Example

curl -X POST "https://www.pando.immo/api/v1/contacts/{id}/email" \
  -H "Authorization: Bearer pando_sk_..." \
  -H "Content-Type: application/json" \
  -d '{
    "subject": "Uw bezoek van morgen",
    "message": "Beste Jonas,\n\nKunnen we morgen om 17 uur afspreken in plaats van 16 uur?",
    "confirm_token": "v1.3f9a...",
    "external_ref": "mail-123"
  }'
Response 201 (200 when it already existed) - created, data: 4 fields
  • sentboolean

    true: the mail left.

  • toemail

    The address it went to.

  • subjectstring

    The subject.

  • sent_atdate-time

    When it was sent.

POST/api/v1/visits/{id}/reschedule/previewscope visits:write

Preview the question to the visitor to move a visit

Step 1 of asking the visitor to move a visit: the exact mail Pando would send (address, subject, text, the current and proposed time, the yes/no buttons) and a confirm_token. Moves, sends and stores nothing. scheduled_at needs Z or an offset.

Path parameters

  • iduuidrequired

    Pando id of the visit (from GET /visits).

Body (JSON)

  • scheduled_atdate-timerequired

    The proposed start, ISO 8601 with Z or an offset (e.g. 2026-10-24T17:00:00+02:00).

  • duration_minutesinteger

    New length; default the current one.

  • messagestring | null

    Your own words above the question.

Example

curl -X POST "https://www.pando.immo/api/v1/visits/{id}/reschedule/preview" \
  -H "Authorization: Bearer pando_sk_..." \
  -H "Content-Type: application/json" \
  -d '{
    "scheduled_at": "2026-10-24T17:00:00+02:00"
  }'
Response 200 - data: 12 fields
  • visit_iduuid

    The visit.

  • toemail

    The visitor's address the question goes to.

  • to_namestring

    The visitor's name.

  • languagestring

    The language the mail is written in.

    nl · fr

  • subjectstring

    The subject line.

  • textstring

    The text above the facts: your message, else Pando's greeting and question.

  • factsstring[]

    The lines under the text: the property, the current time and the proposed time, each as "label: value".

  • buttonsstring[]

    The two answer buttons (yes / no). Each carries a one-time link made when the mail is sent.

  • currentdate-time

    The time the visit has now.

  • proposeddate-time

    The proposed time.

  • duration_minutesinteger

    The length the visit gets on a yes.

  • confirm_tokenstring

    Send it to POST /visits/{id}/reschedule with the same scheduled_at, duration_minutes and message. Valid as long as the mail would stay the same.

POST/api/v1/visits/{id}/reschedulescope visits:write

Move a visit, or ask the visitor first

By default (ask_visitor true) the visitor gets a mail from the office with the current and the proposed time and two buttons: yes moves the visit in Pando and the agent's linked calendar, no keeps the old time; the agent gets a phone notification either way. Nothing moves before the visitor's yes. Asking needs the confirm_token of POST /visits/{id}/reschedule/preview with the same scheduled_at, duration_minutes and message: without it the answer is 409 preview_required, with a stale one 409 preview_changed (both carry the preview); nothing moves and nothing is mailed. An address set or changed through the API less than 24 hours ago is refused (409 recipient_recently_set_via_api). With ask_visitor false the visit moves straight away (agreed by phone), no mail is sent and no token is needed. scheduled_at needs Z or an offset.

Path parameters

  • iduuidrequired

    Pando id of the visit (from GET /visits).

Body (JSON)

  • scheduled_atdate-timerequired

    The new start, ISO 8601 with Z or an offset (e.g. 2026-10-24T17:00:00+02:00).

  • duration_minutesinteger

    New length; default the current one.

  • ask_visitorbooleandefault true

    true = mail the visitor and wait for yes (needs confirm_token); false = move now, no mail.

  • messagestring | null

    Your own words above the question (ask_visitor only).

  • confirm_tokenstring

    The confirm_token of POST /visits/{id}/reschedule/preview. Required to ask the visitor; not used with ask_visitor false.

Example

curl -X POST "https://www.pando.immo/api/v1/visits/{id}/reschedule" \
  -H "Authorization: Bearer pando_sk_..." \
  -H "Content-Type: application/json" \
  -d '{
    "scheduled_at": "2026-10-24T17:00:00+02:00",
    "ask_visitor": true,
    "confirm_token": "v1.3f9a..."
  }'
Response 200 - data: 6 fields
  • modestring

    asked = the visitor got a mail to answer yes or no; moved = the visit moved straight away.

    asked · moved

  • visit_iduuid

    The visit.

  • emailemail

    Where the question went (asked only).

  • currentdate-time

    The time the visit has now.

  • proposeddate-time

    The new time.

  • movedboolean

    true when the visit already moved.

POST/api/v1/visits/{id}/email/previewscope visits:write

Preview the visit confirmation or reminder

Step 1 of mailing the visitor the confirmation or reminder of the Pando agenda: the exact mail Pando would send (address, subject, the full text, the calendar invite's file name) and a confirm_token. Sends and stores nothing.

Path parameters

  • iduuidrequired

    Pando id of the visit (from GET /visits or POST /visits).

Body (JSON)

  • kindstringdefault confirmation

    confirmation (the visit is planned) or reminder (the visit is coming up).

    confirmation · reminder

Example

curl -X POST "https://www.pando.immo/api/v1/visits/{id}/email/preview" \
  -H "Authorization: Bearer pando_sk_..." \
  -H "Content-Type: application/json" \
  -d '{
    "kind": "confirmation"
  }'
Response 200 - data: 9 fields
  • visit_iduuid

    The visit.

  • kindstring

    Which mail.

    confirmation · reminder

  • toemail

    The visitor's address the mail goes to.

  • to_namestring

    The visitor's name.

  • languagestring

    The language the mail is written in.

    nl · fr

  • subjectstring

    The subject line.

  • textstring

    The mail as plain text, exactly as it will be sent (office text, house style, signature).

  • attachmentstring

    File name of the calendar invite (.ics) attached to the mail.

  • confirm_tokenstring

    Send it to POST /visits/{id}/email with the same kind. Valid as long as the mail would stay the same.

POST/api/v1/visits/{id}/emailscope visits:write

Mail the visitor the confirmation or reminder

Pando mails the visitor of a planned visit the same confirmation or reminder as the Pando agenda: in the visitor's language, with the office's own text where it set one, in the office's house style and name, a calendar invite (.ics) attached, and replies going to the agent. The agenda then shows it as mailed. Needs the confirm_token of POST /visits/{id}/email/preview for the same kind: when the mail would differ now, the answer is 409 preview_changed with the new preview and nothing is sent. An address set or changed through the API less than 24 hours ago is refused (409 recipient_recently_set_via_api). The same kind again within 10 minutes answers the first send (created false) and mails nothing.

Path parameters

  • iduuidrequired

    Pando id of the visit (from GET /visits or POST /visits).

Body (JSON)

  • kindstringdefault confirmation

    confirmation (the visit is planned) or reminder (the visit is coming up).

    confirmation · reminder

  • confirm_tokenstringrequired

    The confirm_token of POST /visits/{id}/email/preview.

Example

curl -X POST "https://www.pando.immo/api/v1/visits/{id}/email" \
  -H "Authorization: Bearer pando_sk_..." \
  -H "Content-Type: application/json" \
  -d '{
    "kind": "confirmation",
    "confirm_token": "v1.3f9a..."
  }'
Response 201 (200 when it already existed) - created, data: 5 fields
  • sentboolean

    true: the mail left (now, or within the last 10 minutes for the same kind).

  • kindstring

    Which mail.

    confirmation · reminder

  • visit_iduuid

    The visit.

  • toemail

    The visitor's address it went to.

  • sent_atdate-time

    When it was sent.

GET/api/v1/availabilityscope visits:read

Free and busy times of an agent on one day

For one Brussels day and one active agent of the office: the windows where a visit of duration_minutes fits (15-minute steps, 08:00-20:00, never before now), and what keeps the agent busy: planned visits, Pando appointments and busy blocks of the agent's linked calendar (Microsoft, Google, iCloud). The same sources as the clash warning when planning a visit in Pando. A calendar block, or a colleague's appointment, shows a time only.

Query parameters

  • datedaterequired

    The Brussels day, YYYY-MM-DD.

  • agent_iduuid

    The agent (from GET /agents). Default: the signed-in agent, or the agent who made the API key.

  • duration_minutesintegerdefault 30

    Length of the visit to fit.

Example

curl "https://www.pando.immo/api/v1/availability?date=2026-10-29&duration_minutes=45" \
  -H "Authorization: Bearer pando_sk_..."
Response 200 - data: list of 5 fields
  • kindstring

    free = a window where a visit of duration_minutes fits; visit = a planned visit; appointment = a Pando appointment; calendar = busy in the agent's linked calendar.

    free · visit · appointment · calendar

  • fromstring

    Start, Brussels time HH:mm.

  • tostring

    End, Brussels time HH:mm (24:00 = runs past midnight). For free: the last fitting start is to minus duration_minutes.

  • visit_iduuid | null

    The visit (kind visit only).

  • titlestring | null

    Title of the agent's OWN appointment; never for a colleague or a calendar block.

POST/api/v1/leads/{id}/convertscope leads:write

Convert a lead into a contact

The Leads inbox's "Converteren": the lead becomes a contact (a seller lead a seller, a buyer lead a buyer) and is marked converted; with create_property a seller lead with an address also gets a draft property with that contact as seller. Also needs contacts:write (and properties:write for create_property). Only an IMV lead carries its consent along; no other consent is set. When the lead's e-mail already belongs to a contact, the first call answers 409 known_contact with that contact; send its id as existing_contact_id with choice link (the lead joins that contact, nothing on the contact changes) or new (a separate contact). A lead that is already converted answers its contact with created false.

Path parameters

  • iduuidrequired

    Pando id of the lead (from GET /leads).

Body (JSON)

  • create_propertybooleandefault false

    Seller lead with an address: also make a draft property.

  • existing_contact_iduuid | null

    The contact from a 409 known_contact answer.

  • choicestring | null

    With existing_contact_id: link = hang the lead on that contact; new = make a separate contact.

    link · new

Example

curl -X POST "https://www.pando.immo/api/v1/leads/{id}/convert" \
  -H "Authorization: Bearer pando_sk_..." \
  -H "Content-Type: application/json" \
  -d '{
    "create_property": true
  }'
Response 201 (200 when it already existed) - created, data: 5 fields
  • lead_iduuid

    The lead.

  • contact_iduuid

    The contact the lead became (or already was).

  • property_iduuid | null

    The draft property made from the lead's address, if asked and made.

  • outcomestring

    created = a new contact; linked = hung on the existing contact you chose; reused = the contact the lead already had; already_converted = done earlier, nothing changed.

    created · linked · reused · already_converted

  • warningstring | null

    Something that did not work while the conversion itself did (e.g. the draft property).

PATCH/api/v1/contacts/{id}scope contacts:write

Change a contact

Change some fields of a contact, including the search profile that "Matchende kopers" and match_buyers use, and marketing consent carried over from another system (`marketing_consent`). A field left out keeps its value; null clears it (a list: empties it). Opt-out, the consent to be contacted about the own request (gdpr), identity documents, tags and internal notes cannot be changed here. A search profile is only kept on a buyer or renter; changing the role to anything else clears it, as in Pando. A 409 on marketing_consent changes nothing, also not the other fields sent with it.

Path parameters

  • iduuidrequired

    Pando id of the contact (from GET /contacts).

Body (JSON)

Send at least one field.

  • typestring

    Role of the contact.

    seller · buyer · renter · landlord · syndic · notary · notary_buyer · notary_seller · other

  • first_namestring | null

    First name.

  • last_namestring | null

    Last name.

  • company_namestring | null

    Company name.

  • emailemail | null

    E-mail address.

  • phonestring | null

    Phone number.

  • mobilestring | null

    Mobile number.

  • streetstring | null

    Street and number.

  • postal_codestring | null

    Postal code.

  • citystring | null

    City.

  • languagestring

    Language to address the contact in.

    nl · fr · en

  • pipeline_stagestring

    The "Fase" of the contact, as in Pando: only a stage of its role (the role after this change). A new stage shows in the contact's history.

    new · qualifying · under_offer · closing · won · lost · valuation · mandate · for_sale · searching · viewing · offer

  • search_transactionstring | null

    Search profile: buy (sale) or rent.

    sale · rent

  • search_property_typesstring[] | null

    Search profile: kinds of property (apartment, studio, house, terraced_house, semi_detached, detached_villa, mansion, building_land, land, commercial, garage, other).

  • search_min_bedroomsinteger | null

    Search profile: at least this many bedrooms.

  • search_max_pricenumber | null

    Search profile: highest price in EUR.

  • search_min_surfaceinteger | null

    Search profile: at least this living area in m².

  • search_postal_codesstring[] | null

    Search profile: 4-digit postcodes.

  • marketing_consentobject

    Marketing consent carried over from another system ("may this contact be mailed? yes/no"). given true sets marketing_consent_at once: refused with 409 contact_opted_out when the contact unsubscribed or its address is on the office's suppression list; a consent that already exists is kept unchanged and answered. given false withdraws only a consent that came from an import or the API; a consent given in Pando itself is kept and answered with 409 consent_captured_in_pando. Never sets or clears an opt-out. Absent = unchanged.

    • givenbooleanrequired

      true = the contact agreed to receive marketing mail; false = withdraw an imported or API consent.

    • atdate-time

      Only with given true: when the contact agreed, as recorded in the other system. Not in the future, not before 1990. Absent = now.

    • sourcestringrequired

      Short name of the system the answer comes from, e.g. zabun: lower-case letters, digits and single dashes. Stored as "<source>_import".

Example

curl -X PATCH "https://www.pando.immo/api/v1/contacts/{id}" \
  -H "Authorization: Bearer pando_sk_..." \
  -H "Content-Type: application/json" \
  -d '{
    "mobile": "+32 470 12 34 56",
    "search_transaction": "sale",
    "search_max_price": 400000,
    "search_min_bedrooms": 3,
    "search_postal_codes": [
      "2600",
      "2140"
    ],
    "marketing_consent": {
      "given": true,
      "at": "2024-03-01T10:00:00Z",
      "source": "zabun"
    }
  }'
Response 200 - data: 26 fields
  • iduuid

    Pando id of the contact.

  • typestring

    Role of the contact.

    seller · buyer · renter · landlord · syndic · notary · notary_buyer · notary_seller · other

  • first_namestring | null

    First name.

  • last_namestring | null

    Last name.

  • company_namestring | null

    Company name, for a company contact.

  • emailemail | null

    E-mail address.

  • phonestring | null

    Phone number.

  • mobilestring | null

    Mobile number.

  • streetstring | null

    Street and number.

  • postal_codestring | null

    Postal code.

  • citystring | null

    City.

  • languagestring

    Language to address the contact in.

    nl · fr · en

  • sourcestring | null

    Where the contact came from.

  • tagsstring[]

    Free tags.

  • gdpr_consent_atdate-time | null

    When the contact agreed to be contacted about their own request. Never set through the API.

  • marketing_consent_atdate-time | null

    When the contact agreed to receive marketing. Set through the API only with marketing_consent (POST /contacts, PATCH /contacts/{id}).

  • search_transactionstring | null

    Search profile: wants to buy (sale) or rent.

    sale · rent

  • search_property_typesstring[]

    Search profile: kinds of property wanted (empty = any).

  • search_min_bedroomsinteger | null

    Search profile: at least this many bedrooms.

  • search_max_pricenumber | null

    Search profile: highest price in EUR (monthly rent for a renter).

  • search_min_surfaceinteger | null

    Search profile: at least this living area in m².

  • search_postal_codesstring[]

    Search profile: wanted postcodes (empty = anywhere).

  • created_atdate-time

    When the record was created.

  • updated_atdate-time

    When the record last changed.

  • pipeline_stagestring

    The "Fase" of the contact in Pando. Sellers and landlords: new, qualifying, valuation, mandate, for_sale, under_offer, closing, won, lost. Buyers and renters: new, qualifying, searching, viewing, offer, under_offer, closing, won, lost.

    new · qualifying · under_offer · closing · won · lost · valuation · mandate · for_sale · searching · viewing · offer

  • marketing_consentobject

    The marketing consent as it stands after the call.

    • givenbooleanrequired

      true = the contact may receive marketing mail: a consent is recorded and the contact did not unsubscribe.

    • atdate-time | nullrequired

      When the consent was given; null = none.

    • sourcestring | nullrequired

      Where it came from, e.g. zabun_import; null = given in Pando itself, or no consent.

POST/api/v1/offersscope properties:write

Record a bid

Notes a bid on a property of the office, as the Biedingen screen does, always with status pending. Accepting or refusing a bid, and what that does to the property and other bids, stays a decision in Pando: this endpoint never does it. The amount is in EUR with at most 2 decimals. Send your own id as external_ref: the same id with the same bid returns it (created false); with another bid 409 external_ref_conflict.

Body (JSON)

  • property_iduuidrequired

    The property the bid is on.

  • contact_iduuidrequired

    The bidder, a contact of the office.

  • amountnumberrequired

    The bid in EUR (a number, or a decimal string like "350000.00").

  • conditionsstring | null

    Conditions of the bid (e.g. subject to financing).

  • valid_untildate | null

    Until when the bid stands, a day YYYY-MM-DD, today or later.

  • external_refstring | null

    Your own id for this bid.

Example

curl -X POST "https://www.pando.immo/api/v1/offers" \
  -H "Authorization: Bearer pando_sk_..." \
  -H "Content-Type: application/json" \
  -d '{
    "property_id": "6f1c2a9e-1b2c-4d5e-8f90-123456789abc",
    "contact_id": "0a7d4c3b-2e1f-4a5b-9c8d-abcdef012345",
    "amount": 350000,
    "conditions": "Onder opschortende voorwaarde van financiering",
    "external_ref": "bid-7f3a"
  }'
Response 201 (200 when it already existed) - created, data: 10 fields
  • iduuid

    Pando id of the offer.

  • property_iduuid

    The property the offer is on.

  • contact_iduuid

    The bidder (a contact of the office).

  • amountnumber

    The bid in EUR.

  • statusstring | null

    pending = waiting for the seller's decision.

    pending · accepted · rejected · countered · withdrawn

  • valid_untildate | null

    Until when the bid stands.

  • conditionsstring | null

    Conditions of the bid (e.g. financing).

  • decline_reasonstring | null

    Why it was declined, when rejected or withdrawn.

  • created_atdate-time

    When the record was created.

  • updated_atdate-time

    When the record last changed.

POST/api/v1/properties/{id}/notesscope properties:write

Add a note to a property

Adds one dated line ("YYYY-MM-DD Name: text", Brussels day, the acting agent's name) to the property's internal note, the note shown on the property in Pando and edited in its form. Agent-only: never on portals, feeds or reports. The answer carries only the added line. Send your own id as external_ref: the same id with the same text returns the first line (created false); with another text 409 external_ref_conflict.

Path parameters

  • iduuidrequired

    Pando id of the property (from POST /properties or GET /properties).

Body (JSON)

  • bodystringrequired

    The text of the note.

  • external_refstring | null

    Your own id for this note.

Example

curl -X POST "https://www.pando.immo/api/v1/properties/{id}/notes" \
  -H "Authorization: Bearer pando_sk_..." \
  -H "Content-Type: application/json" \
  -d '{
    "body": "Verkoper wil pas na 1 december verhuizen.",
    "external_ref": "note-91c2"
  }'
Response 201 (200 when it already existed) - created, data: 3 fields
  • property_iduuid

    The property.

  • linestring | null

    The line that was added to the property's internal note: "YYYY-MM-DD Name: text" (Brussels day). Never the rest of the note.

  • added_atdate-time

    When the line was added.

GET/api/v1/properties/{id}/candidatesscope properties:read

List the candidates of a property

The contacts who showed interest in a property of the agency (Kandidaten in Pando: asked for information, visited), oldest first, at most 1000. A candidate is not a party of the file (no seller or buyer role). Names and addresses are read through GET /contacts.

Path parameters

  • iduuidrequired

    Pando id of the property (from POST /properties or GET /properties).

Example

curl "https://www.pando.immo/api/v1/properties/{id}/candidates" \
  -H "Authorization: Bearer pando_sk_..."
Response 200 - data: list of 9 fields
  • iduuid

    Pando id of the candidate row.

  • property_iduuid

    The property.

  • contact_iduuid

    The contact who showed interest (from GET /contacts).

  • notestring | null

    What happened, as written by the office ("bezoek", "info gevraagd").

  • sourcestring

    manual = added in Pando or through the API; import = moved over from a previous CRM.

    manual · import

  • first_seen_ondate | null

    First day the contact showed interest, if known.

  • external_refstring | null

    Your own id for the candidate, if you sent one.

  • created_atdate-time

    When the record was created.

  • updated_atdate-time

    When the record last changed.

POST/api/v1/properties/{id}/candidatesscope properties:write

Add a candidate to a property

Adds a contact of the agency to a property's candidates (Kandidaten), with an optional short note and the first day of interest. Sends no mail, makes no task and gives no role in the file. The same as "Kandidaat toevoegen" in Pando, limited to the agents who may edit the property. Send your own id as external_ref: the same id with the same content returns the first candidate (created false); with other content 409 external_ref_conflict.

Path parameters

  • iduuidrequired

    Pando id of the property (from POST /properties or GET /properties).

Body (JSON)

  • contact_iduuidrequired

    The contact (from GET /contacts or POST /contacts).

  • notestring

    What happened ("bezoek", "info gevraagd via Immoweb").

  • first_seen_ondate

    First day of interest (YYYY-MM-DD), not after today.

  • external_refstring | null

    Your own id for this candidate.

Example

curl -X POST "https://www.pando.immo/api/v1/properties/{id}/candidates" \
  -H "Authorization: Bearer pando_sk_..." \
  -H "Content-Type: application/json" \
  -d '{
    "contact_id": "7c9e6679-7425-40de-944b-e07fc1f90ae7",
    "note": "Bezoek, wil tweede bezoek",
    "first_seen_on": "2026-10-02",
    "external_ref": "zabun-cand-881"
  }'
Response 201 (200 when it already existed) - created, data: 9 fields
  • iduuid

    Pando id of the candidate row.

  • property_iduuid

    The property.

  • contact_iduuid

    The contact who showed interest (from GET /contacts).

  • notestring | null

    What happened, as written by the office ("bezoek", "info gevraagd").

  • sourcestring

    manual = added in Pando or through the API; import = moved over from a previous CRM.

    manual · import

  • first_seen_ondate | null

    First day the contact showed interest, if known.

  • external_refstring | null

    Your own id for the candidate, if you sent one.

  • created_atdate-time

    When the record was created.

  • updated_atdate-time

    When the record last changed.

POST/api/v1/properties/{id}/candidates/removescope properties:write

Remove a candidate from a property

Takes a contact off a property's candidates. The contact itself and its history stay. Limited to the agents who may edit the property.

Path parameters

  • iduuidrequired

    Pando id of the property (from POST /properties or GET /properties).

Body (JSON)

  • contact_iduuidrequired

    The contact to take off the candidates.

Example

curl -X POST "https://www.pando.immo/api/v1/properties/{id}/candidates/remove" \
  -H "Authorization: Bearer pando_sk_..." \
  -H "Content-Type: application/json" \
  -d '{
    "contact_id": "7c9e6679-7425-40de-944b-e07fc1f90ae7"
  }'
Response 200: 3 fields
  • property_iduuid

    The property.

  • contact_iduuid

    The contact taken off the candidates (the contact itself stays).

  • removedboolean

    Always true.

GET/api/v1/mandatesscope properties:read

List mandates

The agency's mandates (bemiddelingsopdrachten), newest first: type, status, start and end date, whether signed. Never the fee, commission, prices, negotiated terms or the signature.

Query parameters

  • limitintegerdefault 50

    Rows per page.

  • offsetintegerdefault 0

    Rows to skip.

  • property_iduuid

    Only mandates of this property.

  • statusstring

    Only mandates with this status.

    draft · active · expired · cancelled · sold

Example

curl "https://www.pando.immo/api/v1/mandates?status=active" \
  -H "Authorization: Bearer pando_sk_..."
Response 200 - data: list of 16 fields
  • iduuid

    Pando id of the mandate.

  • property_iduuid

    The property the mandate is for.

  • property_addressstring | null

    Street, number, postal code and city of the property.

  • seller_contact_iduuid

    The client (seller or landlord).

  • buyer_contact_iduuid | null

    The buyer, on a purchase mandate.

  • assigned_touuid | null

    The agent the mandate is assigned to.

  • typestring

    Kind of mandate.

    exclusive · non_exclusive · auction

  • exclusivitystring | null

    Exclusivity as recorded on the mandate, null when not recorded.

    exclusief · co_exclusief · niet_exclusief

  • statusstring

    Status of the mandate.

    draft · active · expired · cancelled · sold

  • start_datedate

    First day of the mandate.

  • end_datedate | null

    Last day of the mandate, null when open-ended.

  • signedboolean

    Whether the mandate is signed.

  • signed_atdate-time | null

    When it was signed.

  • doc_versionstring | null

    v2 = the Pando bemiddelingsopdracht; null = the older one-page document.

    v2

  • created_atdate-time

    When the record was created.

  • updated_atdate-time

    When the record last changed.

GET/api/v1/mandates/{id}scope properties:read

Get a mandate

One mandate of the agency, with the same fields as the list. Never the fee, commission, prices, negotiated terms or the signature.

Path parameters

  • iduuidrequired

    Pando id of the mandate (from GET /mandates).

Example

curl "https://www.pando.immo/api/v1/mandates/{id}" \
  -H "Authorization: Bearer pando_sk_..."
Response 200 - data: 16 fields
  • iduuid

    Pando id of the mandate.

  • property_iduuid

    The property the mandate is for.

  • property_addressstring | null

    Street, number, postal code and city of the property.

  • seller_contact_iduuid

    The client (seller or landlord).

  • buyer_contact_iduuid | null

    The buyer, on a purchase mandate.

  • assigned_touuid | null

    The agent the mandate is assigned to.

  • typestring

    Kind of mandate.

    exclusive · non_exclusive · auction

  • exclusivitystring | null

    Exclusivity as recorded on the mandate, null when not recorded.

    exclusief · co_exclusief · niet_exclusief

  • statusstring

    Status of the mandate.

    draft · active · expired · cancelled · sold

  • start_datedate

    First day of the mandate.

  • end_datedate | null

    Last day of the mandate, null when open-ended.

  • signedboolean

    Whether the mandate is signed.

  • signed_atdate-time | null

    When it was signed.

  • doc_versionstring | null

    v2 = the Pando bemiddelingsopdracht; null = the older one-page document.

    v2

  • created_atdate-time

    When the record was created.

  • updated_atdate-time

    When the record last changed.

POST/api/v1/properties/{id}/description-draftscope properties:write

Draft a property description (AI)

Writes a Dutch, French and English description of the property with Pando's description generator, from the facts stored on the property and, unless use_photos is false, its own photos. Saves nothing: PATCH /properties/{id} with description_nl, description_fr or description_en saves a text. Counts as one AI action of the office's monthly allowance, the same as the button in Pando. A price on request is never given to the model.

Path parameters

  • iduuidrequired

    Pando id of the property (from POST /properties or GET /properties).

Body (JSON)

  • use_photosbooleandefault true

    Let the model look at the property's photos (up to 6).

Example

curl -X POST "https://www.pando.immo/api/v1/properties/{id}/description-draft" \
  -H "Authorization: Bearer pando_sk_..." \
  -H "Content-Type: application/json" \
  -d '{
    "use_photos": true
  }'
Response 200 - data: 6 fields
  • property_iduuid

    The property.

  • nlstring

    Dutch draft (plain text with light markup: blank line, "- " list, **bold**).

  • frstring

    French draft.

  • enstring

    English draft.

  • photos_usedinteger

    How many of the property's photos the model looked at.

  • savedboolean

    Always false: nothing is saved. PATCH /properties/{id} with description_nl, description_fr or description_en saves a text.

POST/api/v1/properties/{id}/document-request/previewscope properties:write

Preview the request for missing seller documents

Step 1 of "Vraag alles op bij de verkoper": the exact mail Pando would send to the seller or landlord asking for every seller document still missing on the property (to, subject, the full text, the documents) and a confirm_token. Sends and stores nothing.

Path parameters

  • iduuidrequired

    Pando id of the property (from POST /properties or GET /properties).

Body (JSON)

  • recipient_contact_iduuid | null

    The seller or landlord to mail. Leave out when the property has exactly one with an e-mail address.

  • languagestring | null

    Language of the mail; default the recipient's own.

    nl · fr

  • messagestring | null

    A personal line in the mail (plain text).

Example

curl -X POST "https://www.pando.immo/api/v1/properties/{id}/document-request/preview" \
  -H "Authorization: Bearer pando_sk_..." \
  -H "Content-Type: application/json" \
  -d '{
    "language": "nl",
    "message": "Alvast bedankt."
  }'
Response 200 - data: 10 fields
  • property_iduuid

    The property.

  • recipient_contact_iduuid

    The seller or landlord the mail goes to.

  • toemail

    The address the mail goes to.

  • to_namestring

    The recipient's name.

  • languagestring

    The language the mail is written in.

    nl · fr

  • subjectstring

    The subject line.

  • textstring

    The mail as plain text, exactly as it will be sent (house style, signature).

  • documentsstring[]

    The documents the mail asks for, as the mail names them.

  • document_idsstring[]

    Pando ids of those document rows.

  • confirm_tokenstring

    Send it to POST /properties/{id}/document-request with the same fields. Valid as long as the mail would stay the same.

POST/api/v1/properties/{id}/document-requestscope properties:write

Send the request for missing seller documents

Step 2: Pando sends the previewed mail, through the office's own mail setup, in its house style and name, replies going to the agent. Send the same recipient_contact_id, language and message as the preview plus its confirm_token: when the mail would differ now (a document came in, a field changed), the answer is 409 preview_changed with the new preview and nothing is sent. The listed documents become "Opgevraagd" only after the mail left. The same external_ref again answers the first send and mails nothing.

Path parameters

  • iduuidrequired

    Pando id of the property (from POST /properties or GET /properties).

Body (JSON)

  • recipient_contact_iduuid | null

    The seller or landlord to mail. Leave out when the property has exactly one with an e-mail address.

  • languagestring | null

    Language of the mail; default the recipient's own.

    nl · fr

  • messagestring | null

    A personal line in the mail (plain text).

  • confirm_tokenstringrequired

    The confirm_token of the preview.

  • external_refstring | null

    Your own id for this send.

Example

curl -X POST "https://www.pando.immo/api/v1/properties/{id}/document-request" \
  -H "Authorization: Bearer pando_sk_..." \
  -H "Content-Type: application/json" \
  -d '{
    "language": "nl",
    "message": "Alvast bedankt.",
    "confirm_token": "v1.3f9a...",
    "external_ref": "docreq-1"
  }'
Response 201 (200 when it already existed) - created, data: 6 fields
  • sentboolean

    Always true: the mail left.

  • toemail | null

    The address it went to.

  • subjectstring

    The subject line.

  • documentsstring[]

    The documents asked for.

  • sent_atdate-time

    When it was sent.

  • status_updatedboolean

    Whether the documents were marked "Opgevraagd" (requested).

GET/api/v1/properties/{id}/portal-changesscope publications:read

Which portals have older data

Step 1 of "Stuur wijzigingen door": per portal where the property's advert is live, whether Pando's data changed since it was last sent. Only while the property is active, under offer, sold or rented. Each portal to send has a confirm_token bound to the property's data as it is now. Sends nothing.

Path parameters

  • iduuidrequired

    Pando id of the property (from POST /properties or GET /properties).

Example

curl "https://www.pando.immo/api/v1/properties/{id}/portal-changes" \
  -H "Authorization: Bearer pando_sk_..."
Response 200 - data: 5 fields
  • property_iduuid

    The property.

  • sendstring[]

    Push portals where the advert is live and Pando's data differs from what was last sent (state changed) or is not known (state unknown). Each has portal, state and the confirm_token for POST /properties/{id}/portal-changes.

  • up_to_datestring[]

    Live push portals that already have the current data.

  • blockedstring[]

    Live adverts Pando cannot update now, with the reason: not_connected, failed or busy.

  • feedsstring[]

    Feed portals: they fetch the data themselves.

POST/api/v1/properties/{id}/portal-changesscope publications:write

Send the changes to one portal

Step 2: sends the property's current data to ONE push portal where its advert is live, the same as "Stuur wijzigingen door" in Pando: the advert is updated in place, never taken offline first. Needs the portal's confirm_token from GET /properties/{id}/portal-changes; when the property changed since, the answer is 409 preview_changed and nothing is sent. A portal that refuses the update keeps the advert online with the previous data (outcome failed).

Path parameters

  • iduuidrequired

    Pando id of the property (from POST /properties or GET /properties).

Body (JSON)

  • portalstringrequired

    The portal, as named in the preview (immoweb, immovlan, immoscoop, zimmo, spotto).

  • confirm_tokenstringrequired

    That portal's confirm_token from the preview.

Example

curl -X POST "https://www.pando.immo/api/v1/properties/{id}/portal-changes" \
  -H "Authorization: Bearer pando_sk_..." \
  -H "Content-Type: application/json" \
  -d '{
    "portal": "immoweb",
    "confirm_token": "v1.3f9a..."
  }'
Response 200 - data: 4 fields
  • property_iduuid

    The property.

  • portalstring

    The portal.

  • outcomestring

    sent = the portal has the new data; queued = waiting in the queue; failed = the portal refused it (the advert stays online with the previous data); up_to_date = nothing to send.

    sent · queued · failed · up_to_date

  • reasonstring | null

    The portal's error code when failed.

4. Connect an AI assistant (MCP)

The same API is available as a remote MCP server, so an AI assistant can work with the agency's data. Every tool is one endpoint above: same scope, same checks, same answer, except that lists default to 20 rows. Writes are logged in the agency's activity log as coming from the AI connection.

MCP URL
https://www.pando.immo/api/v1/mcp
Transport
Streamable HTTP, stateless, POST only
Authentication
Either a Pando API key (Authorization: Bearer pando_sk_..., office-wide, its scopes; 120 requests per minute per key) or an OAuth access token from "Aanmelden met Pando" (Authorization: Bearer pando_at_..., found through https://www.pando.immo/.well-known/oauth-protected-resource; 120 requests per minute per connection). An OAuth token acts as ONE agent of the office with that agent's own rights: "Lezen" gives the read tools, "Lezen en schrijven" adds the write tools (publishing only when the agent may publish), and an agent who may only edit their own files cannot change a colleague's. Without a valid credential the endpoint answers 401 with WWW-Authenticate resource_metadata; a read-only OAuth connection calling a write tool gets 403 insufficient_scope.
Limits
120 calls per minute per key or per sign-in, and at most 3000 per minute from one IP address
# Claude Code
claude mcp add --transport http pando https://www.pando.immo/api/v1/mcp \
  --header "Authorization: Bearer pando_sk_..."

# Cursor (.cursor/mcp.json)
{ "mcpServers": { "pando": { "url": "https://www.pando.immo/api/v1/mcp",
  "headers": { "Authorization": "Bearer pando_sk_..." } } } }

claude.ai: add a custom connector with this URL (or use the install link on the how-to page), sign in with your Pando account and approve. No key is needed. ChatGPT: the Pando app in ChatGPT connects to this same URL with the same sign-in, and gets the same tools with the same rights. Step by step: pando.immo/en/ai.

A key is office-wide. It is made by an owner or admin and acts for the whole office; per-person rights do not apply to it. A sign-in acts as that agent, with their rights. Use a read-only key unless the assistant must write. Create tools require a fresh external_ref per record, so a retried call never creates a second one. Publishing, taking offline and status changes are marked so the assistant asks first.

What the assistant reads, including contact and lead personal data, goes to the AI provider the agency chose; that falls under the agency's own agreement with that provider.

  • list_propertiesList the office's properties (listings), newest first. Filters, all optional and combined: status (draft, active, under_offer, sold, rented, withdrawn), type, transaction_type (sale, rent), postal_code, city (whole name, any case), min_price, max_price (EUR) and min_bedrooms; a price or bedroom filter leaves out properties where that fact is empty. Never contains commission.
  • get_propertyGet one property of the office by its Pando id.
  • upsert_propertyCreates a property in the office. If the office already has a property with this external_ref, that property is updated instead: sent fields replace the stored values, fields left out are kept, and status is ignored (change status with update_property). A new property starts as draft unless status is active. Never publishes to portals.
  • update_propertyChange some fields of a property (absent = unchanged, null = cleared). A status change also updates every portal the property is on: draft or withdrawn takes the adverts offline, sold or rented marks them so.
  • add_property_photoAdd a photo by https URL (JPEG/PNG/WebP, max 12 MB). Pando downloads the URL. The same URL twice returns the existing photo.
  • list_contactsList the office's contacts (buyers, sellers, renters, landlords), newest first, each with its search profile. Filter with type. The fits_* filters (fits_transaction, fits_property_type, fits_postal_code, fits_price, fits_bedrooms) keep only buyers and renters still searching whose search profile fits those facts, by the same rule as "Matchende kopers" in Pando: a fact that breaks a set criterion drops the contact, a fact left out never does.
  • create_contactCreate a contact. Marked as consenting to marketing only with marketing_consent (given true, source e.g. zabun, optional at): refused with contact_opted_out when the address is on the suppression list of the office. The same external_ref again returns the contact unchanged, also its consent.
  • add_contact_noteAdd a note to a contact of the office, shown in the contact's history in Pando. Optional for a history item from another system: occurred_at (the original moment, not in the future; the history sorts on it), kind (call, mail, visit, sms, portal, note: a label), property_id (a property of the office) and agent_id (an active agent of the office shown as author). Sends no mail, makes no task and is not a call log.
  • list_leadsList the office's Leads inbox, newest first. Filter with since (ISO date) and lead_type (seller, buyer). Lead notes are free text typed by the public on web forms.
  • create_leadAdds a lead to the office's Leads inbox with status new; for a new lead the office's agents get a phone notification. Needs a name, email or phone. Sending the same source and external_ref again updates that lead instead of adding a second one, without a new notification.
  • list_publicationsPer portal (Immoweb, Immovlan, ImmoScoop, ...): status, whether it was only simulated, the portal's id and link.
  • publish_propertyStarts publishing a property on one or more portals through the office's own portal accounts, which puts an advert online; some portals charge per new listing. Per portal: a listing the portal would reject is refused with a reason code, a feed portal the office has not activated is refused, and a portal the office has not connected is simulated (nothing is sent). Returns the publication status per portal.
  • unpublish_propertyTake a property offline on ONE portal.
  • list_tasksList the office's tasks, soonest due first, each with the linked property address, contact name and lead name. Filter with status (open, done) and due_before (ISO date).
  • get_briefingUp to 10 ranked items for the signed-in agent (with an API key: the agent who made it), own plus unassigned: decisions first, like the "Beslissen" block of "Actie nodig" (new leads nobody contacted yet, an overdue legal client check), then overdue tasks, overdue dated 'Terug contacteren' and visits without a recorded outcome, then today's visits and tasks. Each item has kind, title, a plain-words reason (why), the due date if any and the ids of the task, lead, contact, property or visit. Days are Brussels calendar days. Then dossier deadlines up to 14 days ahead (overdue ones rank with the overdue work), certificates that expired or expire within 30 days, and per property the seller documents still to request; for an agent these follow the property's assigned agent. Leads need leads:read, visits contacts:read and properties:read, dossier deadlines, certificates and seller documents properties:read. Never contains amounts or commission.
  • list_visitsList the office's visits, soonest first, each with the property address and the visitor's name. Filter with from and to (a Brussels day YYYY-MM-DD, or an ISO date-time with Z or an offset), property_id, contact_id and status (scheduled, completed, cancelled, no_show).
  • plan_visitPlans a visit (bezichtiging) in Pando: a visit of a property of the office with status scheduled, for the given agent or else the signed-in agent (with an API key: the person who made the key). scheduled_at needs Z or an offset. The visit is stored in the office's Pando agenda, where the office's agents see it, and Pando copies it into the work calendar the agent doing the visit linked in Pando (Outlook/Microsoft 365, Google or iCloud; see linked_calendars in list_agents), with the property address and the visitor. An entry made in a phone's or an assistant's own calendar does not reach Pando, the office's agenda or that work calendar. No e-mail is sent to the visitor. There is no overlap check with other visits, the same as planning in the Pando agenda.
  • set_visit_outcomeRecords what happened at one visit of the office, found by its id: sets its status to completed, no_show or cancelled and can store the visitor's interest, the reason they dropped out (kept only when interest is not_interested), written feedback and a rating from 1 to 5. The agent's linked calendar follows, the same as in the Pando agenda: a cancelled visit is removed from it. Fields left out keep their stored value; null erases the stored value. With feedback_visibility team the feedback stays inside the office; with owner it also appears in the report for the seller. Sends no e-mail.
  • create_taskCreate a task, optionally linked to a property, contact or lead of the office. Assigned to the signed-in agent, or with an API key to the person who made the key.
  • searchFind contacts, properties and leads of the office by name, street, city, reference, e-mail or phone (every word must match). Up to 5 of each, with the id to use in other tools.
  • update_taskMark a task done (completed true) or open again (false), and/or move it to tomorrow or next week at its own time of day. Same rules as the Taken screen in Pando.
  • log_contact_activityLog that the agent called a contact (called, no_answer, voicemail, conversation or wrong_number), with an optional short note and property. Shows in the contact's history in Pando.
  • list_offersList the office's offers (biedingen), newest first, with the bid amount in EUR, the property address and the bidder's name. Filter with status (pending = waiting for a decision) and property_id.
  • get_resultsPer agent: leads, visits, offers, mandates and sales this month, quarter or year, with days on market, achieved % of the asking price and personal goals. An owner or admin sees every agent, an agent only themselves. Never revenue or fees.
  • match_buyersThe buyers or renters whose search profile fits a property, best first (up to 10), and how many still search. Same match as "Matchende kopers" in Pando.
  • list_agentsThe office's active agents with name and role, with the id to use for update_lead (assigned_to) or plan_visit (agent_id). is_you marks the signed-in agent. linked_calendars lists the calendars (microsoft = Outlook/Microsoft 365, google, icloud) the agent linked in Pando: visits planned in Pando or with plan_visit are written into those calendars by Pando; empty means none is linked.
  • update_leadHand a lead to an active agent of the office (or to nobody with null) and/or move it to another stage: new, rejected, or one of the office's middle stages (contacted, appointment, or the office's own stage ids). Same rules as the Leads inbox in Pando. Converting a lead into a contact is convert_lead.
  • get_dossierThe steps of a property's dossier (Voortgang in Pando) in the office's own order: done, not applicable, open, optional or the legal client check still open, with deadline days and the step count.
  • preview_emailStep 1 of e-mailing a contact: the exact mail Pando would send (address, subject, the full text in the office's house style with the agent's signature) with a confirm_token. Sends and stores nothing. send_email sends it.
  • send_emailSends the mail of preview_email from the agent to a contact of the office, through the office's own mail setup, in its house style with the agent's signature; replies go to the agent. Needs the same subject and message as the preview and its confirm_token; when the mail would differ now, nothing is sent and the answer is preview_changed with the new preview. An address set or changed through create_contact, update_contact or convert_lead less than 24 hours ago is refused (recipient_recently_set_via_api); the same mail sent from Pando itself works. Recorded as a note on the contact. The same external_ref again never sends twice.
  • preview_reschedule_visitStep 1 of asking the visitor to move a planned visit: the exact mail Pando would send (address, subject, text, current and proposed time, yes/no buttons) with a confirm_token. Moves, sends and stores nothing. reschedule_visit with ask_visitor true sends it.
  • reschedule_visitProposes a new time for a planned visit. ask_visitor true (default): the visitor gets the mail of preview_reschedule_visit with yes/no buttons; yes moves the visit in Pando and the agent's calendar, no keeps the old time, and the agent gets a phone notification. Asking needs the preview's confirm_token with the same scheduled_at, duration_minutes and message: without it the answer is preview_required, with a stale one preview_changed, and nothing moves or is mailed. An address set or changed through create_contact, update_contact or convert_lead less than 24 hours ago is refused (recipient_recently_set_via_api); the same mail sent from Pando itself works. ask_visitor false moves the visit straight away without a mail and without a token.
  • preview_visit_mailStep 1 of mailing the visitor of a planned visit the confirmation (kind confirmation) or reminder (kind reminder) of the Pando agenda: the exact mail Pando would send (address, subject, full text, the calendar invite's file name) with a confirm_token. Sends and stores nothing. send_visit_mail sends it.
  • send_visit_mailPando mails the visitor of a planned visit the confirmation or the reminder of preview_visit_mail, the same mail the Pando agenda sends: in the visitor's language, with the office's own text where it set one, in the office's house style and name, with a calendar invite attached; replies go to the agent. Needs the same kind and the preview's confirm_token; when the mail would differ now, nothing is sent and the answer is preview_changed. An address set or changed through create_contact, update_contact or convert_lead less than 24 hours ago is refused (recipient_recently_set_via_api); the same mail sent from Pando itself works. The agenda then shows the visit as mailed. The same kind again within 10 minutes mails nothing and returns the first send. The visit must be planned and still to come, and the visitor needs an e-mail address.
  • find_free_slotsFor one Brussels day (date YYYY-MM-DD) and one agent (agent_id from list_agents; default the signed-in agent): the windows where a visit of duration_minutes (default 30) fits, in 15-minute steps between 08:00 and 20:00 and never before now, plus what keeps the agent busy: planned visits, Pando appointments and busy blocks of the agent's linked calendar. The same sources as the clash warning when planning a visit in Pando. A visit planned with plan_visit lands in the office's Pando agenda and in the agent's linked work calendar. A calendar block or a colleague's appointment shows a time only.
  • convert_leadThe Leads inbox's "Converteren": the lead becomes a contact (seller or buyer, as the lead) and is marked converted; with create_property a seller lead with an address also gets a draft property with that contact as seller. Only an IMV lead carries its consent along. When the lead's e-mail already belongs to a contact, the answer is the error known_contact with that contact; calling again with existing_contact_id and choice link hangs the lead on that contact (nothing on it changes), choice new makes a separate contact. An already converted lead returns its contact and changes nothing. Needs the contacts write right too.
  • update_contactChange some fields of a contact of the office, found by its id: name, company, e-mail, phone, mobile, address, language, role (type), stage (pipeline_stage, the "Fase" in Pando: only a stage of the contact's role, else stage_not_for_type) and the search profile (search_transaction, search_property_types, search_min_bedrooms, search_max_price, search_min_surface, search_postal_codes) that match_buyers and "Matchende kopers" use. Fields left out keep their value; null clears one (a list: empties it). marketing_consent carries over consent from another system: given true sets it once (an existing consent is kept; refused with contact_opted_out after an unsubscribe or for a suppressed address), given false withdraws only an imported or API consent (a consent given in Pando itself is kept: consent_captured_in_pando); a refusal changes nothing. Opt-out, gdpr consent, identity documents, tags and internal notes cannot be changed. A search profile is only kept on a buyer or renter. The answer carries marketing_consent as it stands.
  • record_offerRecords a bid (bieding) in EUR from a contact of the office on a property of the office, with optional conditions and a last valid day, always with status pending (waiting for a decision). Accepting or refusing a bid is not possible with this tool; that stays a decision in Pando. Shows on the property's Biedingen in Pando and in list_offers.
  • add_property_noteAdds one dated line (date, the agent's name, the text) to the internal note of a property of the office, the note shown on the property in Pando. Agent-only: never on portals, feeds or reports. Changing the property is limited to the agents who may edit it, as in Pando. The answer holds only the added line.
  • list_property_candidatesThe contacts who showed interest in a property of the office (Kandidaten in Pando: asked for information, visited), oldest first, with the office's short note and the first day of interest. A candidate has no role in the file (not a seller or buyer). Names come from list_contacts.
  • add_property_candidateAdds a contact of the office to a property's candidates (Kandidaten), with an optional short note and first day of interest. Sends no mail, makes no task and gives no role in the file. Changing the property is limited to the agents who may edit it, as in Pando. A contact that already is a candidate of the property gives already_candidate.
  • remove_property_candidateTakes a contact off a property's candidates. The contact itself and its history stay. Limited to the agents who may edit the property.
  • list_mandatesList the office's mandates (bemiddelingsopdrachten), newest first, with the property address, type, status, start and end date and whether signed. Filter with property_id and status (draft, active, expired, cancelled, sold). Never contains the fee, commission, prices, negotiated terms or the signature.
  • get_mandateOne mandate of the office by its Pando id: property address, type, status, start and end date and whether signed. Never contains the fee, commission, prices, negotiated terms or the signature.
  • draft_property_descriptionPando's description generator writes a Dutch, French and English text for a property of the office from the facts stored on it and, unless use_photos is false, its photos. Nothing is saved: update_property with description_nl, description_fr or description_en saves a text. Counts as one AI action of the office's monthly allowance, the same as the button in Pando.
  • preview_seller_document_requestStep 1 of "Vraag alles op bij de verkoper": the exact mail Pando would send to the seller or landlord of a property asking for every seller document still missing (recipient, language, subject, full text, the documents), with a confirm_token. Sends and stores nothing. request_seller_documents sends it.
  • request_seller_documentsPando mails the seller or landlord the request from preview_seller_document_request, in the office's house style and name, replies going to the agent. Needs the same recipient_contact_id, language and message as the preview and its confirm_token; when the mail would differ now, nothing is sent and the answer is preview_changed with the new preview. The documents become "Opgevraagd" only after the mail left. An address set or changed through create_contact, update_contact or convert_lead less than 24 hours ago is refused (recipient_recently_set_via_api); the same mail sent from Pando itself works. The same external_ref again never mails twice.
  • preview_portal_changesStep 1 of "Stuur wijzigingen door": per portal where a property's advert is live (Immoweb, Immovlan, ImmoScoop, ...), whether Pando's data changed since it was last sent, only while the property is active, under offer, sold or rented. Each portal to send has a confirm_token for send_portal_changes. Sends nothing.
  • send_portal_changesSends a property's current data to ONE portal where its advert is live, the same as "Stuur wijzigingen door" in Pando: the public advert is updated in place, never taken offline first. Needs that portal's confirm_token from preview_portal_changes; when the property changed since, nothing is sent and the answer is preview_changed. A portal that refuses the update keeps the advert with the previous data (outcome failed).

Publishing and the sandbox

Pando publishes a listing through the agency's own portal accounts. Each portal (Immoweb, Immovlan, ImmoScoop and others) needs its own contract with the agency; Pando does the technical side, not the contract.

Sandbox. Until the agency connects a portal in Pando, publishing to it is simulated: nothing is sent, and the result says simulated: true. What the portal would refuse is still checked and returned, so you can build and test the whole flow (create, photos, publish, status, take offline) without an advert going live.

A typical flow: POST /properties with your own external_ref, a POST /properties/{id}/photos per photo, POST /properties/{id}/publish, then read GET /properties/{id}/publications. Changed the listing? Send it again and publish again. Sold? PATCH the status. The API does not start Pando's automations (such as mails to matching buyers).

Questions

Mail info@pando.immo.