RESO Web API

Name: RESO Web API
Brand: RESO Web API
Availability: InStock

✓ Official Vendor SpecE CommerceStorefrontbearer7 EndpointsREST

For Agents

Programmatically list properties, get property by listing key. Covers 7 operations with bearer authentication.

Use for: I need to properties, I want to property by listing key, Search for members/agents, Find all offices

Install Jentic One Beta

Connect the RESO Web API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the RESO Web API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with RESO Web API.

List Properties

Get Property by Listing Key

Integrate RESO Web API into automated workflows

Query and filter RESO Web API records by parameters

GET STARTED

Start building with RESO Web API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use RESO Web API for, with concrete tasks.

★ E-Commerce Operations

Use the RESO Web API to perform e commerce operations programmatically. The API provides 7 endpoints covering core functionality including list properties, get property by listing key, list members/agents.

Call GET /Property to list properties

Automated Media Management

Automate media operations by combining multiple RESO Web API endpoints. Agents can get property by listing key and then list members/agents in a single workflow.

Call GET /Property('{listingKey}') to get property by listing key, then verify the result

AI Agent Integration via Jentic

AI agents discover and call RESO Web API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.

Search Jentic for 'list properties', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

7 endpoints — reso web api standard based on odata v4 for real estate data exchange.

METHOD

PATH

DESCRIPTION

GET

/Property

List Properties

GET

/Property('{listingKey}')

Get Property by Listing Key

GET

/Member

List Members/Agents

GET

/Office

List Offices

GET

/Media

List Media

GET

/OpenHouse

List Open Houses

GET

/$metadata

Get Service Metadata

GET

/Property

List Properties

GET

/Property('{listingKey}')

Get Property by Listing Key

GET

/Member

List Members/Agents

GET

/Office

List Offices

GET

/Media

List Media

GET

/OpenHouse

List Open Houses

Why Jentic?

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

Credential isolation

RESO Web API bearer credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'list properties') and Jentic returns the matching RESO Web API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct RESO Web API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Shopify

Alternative e commerce API

Choose Shopify when you need a different approach to e commerce operations

Alternative

Stripe

Alternative e commerce API

Choose Stripe when you need a different approach to e commerce operations

FAQs

Specific to using RESO Web API through Jentic.

What authentication does the RESO Web API use?

The RESO Web API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.

Can I list properties with the RESO Web API?

Yes. Use the GET /Property endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the RESO Web API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I list properties through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'list properties'. Jentic returns the matching RESO Web API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the RESO Web API have?

The RESO Web API exposes 7 endpoints covering media, member, metadata operations.