How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Bridge Interactive RESO Web API API

The RESO Web API API from Bridge Interactive — 7 operation(s) for reso web api.

Bridge Interactive RESO Web API API is one of 5 APIs that Bridge Interactive publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include RESO Web API. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 7 operations across 7 paths, and defines 2 schemas. It is described by OpenAPI 3.2.0, at version v2.

Requests are made against a single base URL, https://api.bridgedataoutput.com/api/v2.

7 operations 7 paths 2 schemas 7 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v2
Base URL
https://api.bridgedataoutput.com/api/v2
Authentication
HTTP Bearer
Terms of Service
Resource Areas
1

Authentication & Security 1

Bridge Interactive RESO Web API API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — Server access token issued from the Bridge Dashboard under Data Access API Access Tokens. Sent as "Authorization: Bearer " or as an accesstoken query parameter.

Paths & Operations 7

Across 7 paths, the API surfaces 7 operations — 7 GET. Each is listed below with its method, path, parameters, and response codes.

RESO Web API 7
GET
/OData/{dataset_id}/$metadata
RESO Web API metadata document
getResoMetadata 2 params → 200
GET
/OData/{dataset_id}/Property
RESO Property collection (OData)
getResoProperty 8 params → 200401
GET
/OData/{dataset_id}/Property/replication
RESO Property replication endpoint
getResoPropertyReplication 4 params → 200
GET
/OData/{dataset_id}/Member
RESO Member collection (OData)
getResoMember 7 params → 200
GET
/OData/{dataset_id}/Office
RESO Office collection (OData)
getResoOffice 7 params → 200
GET
/OData/{dataset_id}/OpenHouse
RESO OpenHouse collection (OData)
getResoOpenHouse 7 params → 200
GET
/OData/{dataset_id}/Media
RESO Media collection (OData)
getResoMedia 7 params → 200

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are Error (3 properties), ODataCollection (3 properties). Each schema is shown below with its type and property counts.

ODataCollection
object
OData collection response for RESO Web API resources.
3 properties
Error
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

bridge-interactive-reso-web-api-api-openapi.yml Raw ↑

Other APIs Bridge Interactive publishes across the network.

Bridge Interactive Agents API
Bridge Interactive Listings API
Bridge Interactive Offices API
Bridge Interactive Open Houses API
Where this information came from

This is an independent, third-party profile of Bridge Interactive RESO Web API API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.