EasyBroker API

Name: EasyBroker API API
Brand: EasyBroker API
Availability: InStock

✓ Official Vendor SpecCRMContact ManagementapiKey7 EndpointsREST

For Agents

Manage real estate property listings, capture buyer contact requests, and look up location reference data on the EasyBroker platform.

Quickstart

Get started with EasyBroker API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create a real estate property listing on easybroker"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with EasyBroker API API.

List and paginate active property listings with filters

Create a new property listing with photos, price, and address fields

Update price, status, or descriptive fields on an existing property

Retrieve full property detail by property ID for portal display

GET STARTED

Start building with EasyBroker API API

Explore with Jentic

View OpenAPI Document

Use for: Create a new property listing in EasyBroker for a 3-bedroom apartment, Update the price on an existing EasyBroker listing, List all active properties in my EasyBroker portfolio, Capture a contact request from a buyer interested in a listing

Not supported: Does not handle commission calculations, broker payroll, MLS syndication, or transactional escrow — use for EasyBroker property listings, contact requests, and location lookups only.

EasyBroker is a real estate CRM and listing platform widely used by Latin American brokerages to manage property catalogues and lead pipelines. The API exposes endpoints for creating and updating property listings, capturing inbound contact requests, and reading the location reference data used to tag listings. It is used by portals, lead-gen sites, and AI assistants that need to push or pull real estate inventory programmatically.

Use Cases

Patterns agents use EasyBroker API API for, with concrete tasks.

★ Listing syndication to a portal

Real estate portals and aggregator sites pull active listings from EasyBroker via GET /properties to keep their catalogue in sync with the source brokerage. Each listing's full record can be fetched on demand from /properties/{property_id} when a user clicks through, avoiding stale data.

List all EasyBroker properties updated in the last 24 hours and return their IDs and titles.

Lead capture from a marketing landing page

When a prospect submits a contact form on a brokerage's landing page, an agent calls POST /contact_requests with the property ID, prospect name, email, and message. The lead lands in the broker's EasyBroker pipeline immediately so an agent can follow up while interest is fresh.

Create a contact request against property 12345 with name 'Maria Lopez', email 'maria@example.com', and message 'Interested in viewing this weekend'.

Bulk listing creation from a spreadsheet

Brokerages onboarding to EasyBroker often start with an Excel inventory. An agent reads each row and calls POST /properties to create the listing with title, price, location ID, and description. Failed rows can be retried by inspecting the response error and the address resolved against /locations.

Given a CSV row with title, price, location ID, and description, create the matching EasyBroker property and return the new property ID.

Agent-driven listing maintenance

An AI agent can respond to natural-language brokerage commands like 'mark this property as sold' or 'reduce the price of listing 12345 by 5 percent'. Through Jentic, the agent matches the intent to PATCH /properties/{property_id} and executes the right partial update without the user editing fields manually.

Reduce the price on EasyBroker property 12345 by 5 percent and confirm the new price in the response.

Key Endpoints

7 endpoints — easybroker is a real estate crm and listing platform widely used by latin american brokerages to manage property catalogues and lead pipelines.

METHOD

PATH

DESCRIPTION

GET

/properties

List property listings

POST

/properties

Create a new property listing

GET

/properties/{property_id}

Get property details

PATCH

/properties/{property_id}

Update a property listing

GET

/contact_requests

List inbound contact requests

POST

/contact_requests

Capture a buyer contact request

GET

/locations

List canonical locations

GET

/properties

List property listings

POST

/properties

Create a new property listing

GET

/properties/{property_id}

Get property details

PATCH

/properties/{property_id}

Update a property listing

GET

/contact_requests

List inbound contact requests

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

EasyBroker X-Authorization keys are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — the raw key never enters the agent's context, prompt, or logs.

Intent-based discovery

Agents search Jentic for intents like 'create a real estate listing' and Jentic returns the matching EasyBroker operation with its input schema, so the agent calls POST /properties without browsing EasyBroker docs.

Time to first call

Direct EasyBroker integration: 1-2 days to wire auth, listing payloads, and lead capture. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

HubSpot CRM

General-purpose CRM with deeper pipeline automation

Choose HubSpot when leads need to flow into a non-real-estate CRM or when richer marketing automation around inquiries is required; pick EasyBroker when listings and broker-side workflows are the primary need.

Alternative

Salesforce API

Enterprise CRM backbone for larger brokerages

Choose Salesforce for multi-office brokerages with custom pipelines and reporting needs that exceed EasyBroker's standard CRM.

Complementary

Google Maps Platform

Geocoding and place enrichment for property addresses

Use Google Maps alongside EasyBroker to enrich property addresses with coordinates, neighbourhood data, and nearby points of interest.

FAQs

Specific to using EasyBroker API API through Jentic.

What authentication does the EasyBroker API use?

EasyBroker uses an API key passed in the X-Authorization HTTP header. Through Jentic, the key is stored encrypted in the vault (MAXsystem) and attached to each request at execution time, so the raw key is never visible to the agent.

Can I create and update property listings with the EasyBroker API?

Yes. POST /properties creates a new listing with title, price, location, and description fields, and PATCH /properties/{property_id} updates any subset of those fields on an existing record. GET /properties/{property_id} returns the canonical detail view.

What are the rate limits for the EasyBroker API?

The spec does not publish numeric rate limits. EasyBroker enforces per-account throttling on listing writes — if you hit a 429, back off and retry, or contact EasyBroker support to raise the cap on your plan.

How do I capture a buyer lead through Jentic?

Search Jentic for 'capture a real estate lead', load the schema for POST /contact_requests, then execute with the property ID and prospect details. The full flow is: pip install jentic, then await client.search, await client.load, await client.execute.

Does the EasyBroker API expose agent or commission data?

This 7-endpoint surface covers properties, contact requests, and locations. Broker user accounts, commission splits, and pipeline stages are managed in the EasyBroker web app and are not exposed by these endpoints.