API v1: Inquiries & leads

Both endpoints are create-only — there is no list/get/update for inquiries or leads through the API. They auto-create or match a contact from the fields you send.

Create an inquiry

POST /api/v1/inquiries

For an inquiry raised from a website or another external source (e.g. a "Contact about this listing" form).

Required: message.

{
  "first_name": "Ivan",
  "last_name": "Georgiev",
  "email": "[email protected]",
  "phone_number": "+359888111222",
  "property_id": "b2b1e6b0-...",
  "message": "Is this property still available for viewing this weekend?",
  "source": "website"
}

source defaults to "website" if omitted. Response: 201 Created.

Create an inbound lead

POST /api/v1/leads

Generic inbound lead endpoint for Meta Lead Ads, Google Ads, website forms, or any external source — most commonly wired through Zapier.

Required: source.

{
  "first_name": "Georgi",
  "last_name": "Petrov",
  "email": "[email protected]",
  "phone_number": "+359888765432",
  "source": "zapier",
  "purpose": "buy",
  "budget_min": 100000,
  "budget_max": 250000
}

Response: 201 Created.

Choosing between them

• Use /inquiries when the source is a specific property (a "contact about this listing" form) — it links the message to property_id.
• Use /leads for a general capture form or ad platform lead that isn't tied to one listing, and carries purpose/budget instead of a free-text message.

Both endpoints emit the lead.inbound_received webhook event on success — see Webhooks and automation connectors.