Overview

The Create Saved Search API lets you set up automated property search alerts for CRM contacts. Define search criteria (city, price range, bedrooms, property type, etc.), choose a notification frequency, and the platform will automatically run the search on schedule — notifying the contact when new matching listings appear.

Each saved search stores a baseline snapshot of current results on creation, so subsequent runs can detect genuinely new listings rather than re-sending the entire result set.

How It Works

1. Authentication — Validates your API key and establishes the user database connection
2. Contact Validation — Confirms the contact exists in your CRM under the specified organization
3. Filter Sanitization — Validates and sanitizes all search filters against the allowed filter set
4. Idempotency Check — Rejects duplicate searches if the same contact already has a saved search with identical filters
5. Limit Check — Enforces a maximum of 10 saved searches per contact
6. Search Creation — Inserts the saved search record with calculated next-run schedule
7. Signal Tracking — Records a reso_saved_search_created signal on the contact for engagement scoring
8. Baseline Snapshot — Optionally executes the search immediately to capture the current matching listings as a baseline

Request

Endpoint: https://app.zyntrohq.com/apis/public/real_estate/createSavedSearch.php

Method: POST

Content-Type: application/json

Request Fields

Filter Fields

Sample Request

{
  "api_key": "your_zyntro_api_key",
  "org_id": "your-org-uuid",
  "brand_id": 1,
  "member_id": "your-member-uuid",
  "contact_id": "contact-uuid",
  "search_name": "Barrie Detached 3+ BR under $1M",
  "filters": {
    "cities": ["Barrie", "Innisfil"],
    "property_type": "Residential",
    "property_sub_types": ["Detached", "Semi-Detached"],
    "transaction_type": "for_sale",
    "min_price": 500000,
    "max_price": 1000000,
    "min_beds": 3,
    "min_baths": 2
  },
  "frequency": "weekly",
  "notification_email": "[email protected]",
  "created_by": "member",
  "skip_baseline": false
}

Response

Success Response

{
  "status": "success",
  "message": "Saved search created",
  "data": {
    "uuid": "a1b2c3d4-e5f6-4a7b-8c9d-e0f1a2b3c4d5",
    "name": "Barrie Detached 3+ BR under $1M",
    "filters": {
      "cities": ["Barrie", "Innisfil"],
      "property_type": "Residential",
      "property_sub_types": ["Detached", "Semi-Detached"],
      "transaction_type": "for_sale",
      "min_price": 500000,
      "max_price": 1000000,
      "min_beds": 3,
      "min_baths": 2
    },
    "frequency": "weekly",
    "notification_email": "[email protected]",
    "next_run_at": "2026-04-02 14:30:00",
    "baseline_results": 47
  }
}

Response Fields

Error Responses

// Missing required fields
{"status": "error", "message": "api_key is required, contact_id is required"}

// Invalid API key
{"status": "error", "message": "Invalid API key"}

// Contact not found
{"status": "error", "message": "Contact not found"}

// No valid filters
{"status": "error", "message": "At least one valid filter is required"}

// Duplicate filters
{
  "status": "error",
  "message": "Duplicate search — contact already has a saved search with identical filters",
  "existing_uuid": "existing-search-uuid",
  "existing_name": "Existing Search Name"
}

// Maximum searches reached
{"status": "error", "message": "Contact has reached the maximum of 10 saved searches"}

Behavior Details

Idempotency

The API prevents duplicate saved searches. If a contact already has an active saved search with the exact same filter set, the request is rejected and the existing search UUID is returned. This means you can safely retry creation requests without worrying about duplicates.

Baseline Snapshot

By default, the API immediately executes the search against your MLS data and stores the matching listing IDs as a baseline. When the scheduled cron runs the search later, it compares new results against this baseline to identify genuinely new listings — so contacts only get notified about properties they haven't seen before.

Set skip_baseline to true if you want the first scheduled run to treat all matching results as new (useful for newly onboarded contacts who want to see everything).

Signal Tracking

Every saved search creation records a reso_saved_search_created signal on the contact's engagement timeline. This feeds into Zyntro's engagement scoring and segmentation intelligence — a contact who sets up saved searches is demonstrating active buyer intent.

Frequency Schedule

Limits

• Maximum 10 saved searches per contact (excluding deleted searches)
• Only whitelisted filter keys are accepted — unknown keys are silently dropped
• Null or empty filter values are stripped during sanitization

Best Practices

• Name searches descriptively. "Barrie Detached 3+ BR under $1M" is far more useful than "Search 1" — both for your team and for the contact receiving alerts.
• Start with weekly frequency. Daily alerts can overwhelm contacts in slower markets. Start weekly and let contacts request more frequent updates if they're actively buying.
• Use array filters for flexibility. cities and property_sub_types let you cover broader criteria in a single search, reducing the number of saved searches needed per contact.
• Don't skip baseline for existing contacts. The baseline prevents re-sending listings the contact may have already seen. Only skip it for brand-new contacts who want the full picture.
• Let the duplicate check work for you. The API returns the existing search UUID when duplicates are detected — use this to redirect rather than error-handling.