Bright serves its listing data through its own RESO Web API. We sync it into your WordPress, Laravel or custom site and keep it current every 2 to 3 hours.
POST /token client_credentialsGET /$metadataGET /Property?$top={max}@odata.nextLink$filter=ModificationTimestamp gt {last}Bright covers a big, mixed market, from city rowhouses to rural land. A plugin that worked for one county starts to creak at that scale, and the usual answer is a rebuild quote. We have synced this board's feed before, on a multi MLS platform we built and ran from 2018 to 2025.
Bright MLS is the Mid-Atlantic MLS, covering parts of six states and Washington, D.C. It formed from a merger of regional MLSs and launched with that six state service area.
Bright distributes data through its own RESO Web API rather than leaning on a single outside platform. Brokers and vendors license feeds through Bright's Content Licensing team.
In 2025 Bright, First MLS and MIAMI REALTORS announced that their subscribers could search and view listings across all three organizations. That is MLS access for agents. Website feeds are still licensed by Bright.
The board decides which platform carries its feed. Each route has its own login, paging and limits, and its own page here.
Bright licenses its own data. You, or the developer working for you, ask Bright for the feed that fits the site.
Ask Bright's Content Licensing team for a feed, and say what the site will show and who will build it.
Pick the use that fits, such as IDX for public listing pages. The licence sets the fields, statuses and display rules.
Bright sends its licence agreement. Any fee is set there.
Bright issues an OAuth 2 client ID and secret for its Web API. If you already hold a feed, Bright's FAQ says Web API access attaches to it.
The sync is built against the metadata your licence returns, checked against Bright, and then your pages switch.
Bright's API follows the RESO standard, with Bright's own fields added. Your licence decides what you see of it.
01GET $metadata lists every resource, field and lookup your credentials can read, including Bright specific fields.
02Property records named and shaped by the RESO Data Dictionary, filtered by your licence.
03Agent and office data where the licence allows, or rosters built from the listing feed when it does not.
04Large results come a page at a time, with @odata.nextLink pointing to the next one.
05Regular runs filter on ModificationTimestamp and track the last value seen.
06A daily purge compares listing keys against your copy, and stops with an alert if the feed returns too few.
Bright keeps most of its feed documentation behind a developer login. These are the points it states in public, and what the sync does with them.
Bright's developer documentation says it adds its own fields next to the RESO ones in the metadata. They get their own small filter class on top of the shared parser.
Feed access is requested through Bright's Content Licensing team. The licence sets which fields and statuses arrive, so the sync is built against the metadata your licence returns.
Bright's IDX listings carry its own disclaimer text. It is shown per board with the last updated time, and IDX opt out flags are honoured.
The Bright client secret lives in server config, not plugin settings editors can see. A server cron job runs the sync into its own tables, so the theme renders listings without calling Bright on each page view. Bright's disclaimer sits in one template part.
Bright gets a config entry and a filter class for its own fields on top of the shared parser. Scheduled queued jobs run the changes pull, the weekly re-sync and the daily purge, and models read the listing tables.
Any stack that can request an OAuth token and run a schedule will do. Bright's footprint spans several states, so map search runs on a local search index with pin clustering rather than live API calls.
Your listings never go blank. The new sync runs beside whatever feeds the site today, and we only switch when the two match.
We check your Bright licence, your API credentials and what the site needs to show.
It fills its own tables while your current listings stay up.
Counts, statuses, photos and rosters checked against the feed.
Pages read from the new sync. The old plugin or script is removed.
Bright serves its feed through its own RESO Web API, and that is the route it documents. We did not find Bright publishing a Trestle, Bridge or MLS Grid option for broker feeds. The audit checks which route your licence uses.
If you hold an older feed from Bright, its FAQ says the Web API can be added to it without a new contract. The audit confirms which credentials you have and what they return.
Your site's address, what it runs on, and which MLS or feed you have access to.
Access, fields, photos, rosters, and how your platform stores listings.
What syncs, how often, what shows where, and a fixed price for the build.
If you go ahead, the $499 comes off the integration.
We are an independent developer. We are not affiliated with, or certified by, any MLS or data provider named on this page.
Send the site's address and the feed you have access to. The audit gives you a written plan and a fixed quote.