Developer Documentation
Platform Overview
API Services
Overview Accounts Accounts: Associations Accounts: Metadata Accounts: Profile Appstore: Users Broker Distributions Broker Tours Consumers Consumers: Linked Agents Contacts Contacts: Activity Contacts: Export Contacts: Tags Contacts: Portal Accounts Developers: Identities Developers: Keys Developers: Authorizations Developers: Billing Summary Developers: Change History Developers: Domains Developers: News Feed Webhooks Developers: Roles Developers: Syndications Developers: Templates Developers: Usage Detail Developers: Usage Summary Devices Flexmls: Email Links Flexmls: Listing Meta Origins Flexmls: Listing Meta Translations Flexmls: Listing Meta Field List Translations Flexmls: Listing Reports Flexmls: Mapping Layers Flexmls: Mapping Shapegen IDX IDX Links Listing Carts Listing Carts: Portal/VOW Carts Incomplete Listings Incomplete Listings: Documents Incomplete Listings: Documents Metadata Incomplete Listings: Document Uploads Incomplete Listings: Floor Plans Incomplete Listings: FloPlans Incomplete Listings: Photos Incomplete Listings: Photos Metadata Incomplete Listings: Photo Uploads Incomplete Listings: Rooms Incomplete Listings: Tickets Incomplete Listings: Units Incomplete Listings: Videos Incomplete Listings: Videos Metadata Incomplete Listings: Virtual Tours Incomplete Listings: Virtual Tours Metadata Listings Listings: Clusters Listings: Documents Listings: Documents Metadata Listings: Floor Plans Listings: FloPlans Listings: Historical Listings: History Listings: Notes Listings: Search Parameters Listings: Open Houses Listings: Photos Listings: Photos Metadata Listings: Photo Uploads Listings: Document Uploads Listings: Rental Calendar Listings: Rooms Listings: Rules Listings: Tour of Homes Listings: Tickets Listings: Units Listings: Validation Listings: Videos Listings: Videos Metadata Listings: Virtual Tours Listings: Virtual Tours Metadata Listing Meta: Custom Fields Listing Meta: Custom Field Groups Listing Meta: Field Order Listing Meta: Field Relations Listing Meta: Property Types Listing Meta: Rooms Listing Meta: Standard Fields Listing Meta: Units Registered Listings Market Statistics News Feed News Feed: Curation News Feed: Events News Feed: Metadata News Feed: Restrictions News Feed: Schedule News Feed: Settings News Feed: Templates Open Houses Overlays Overlays: Shapes Portals Preferences Saved Searches Saved Searches: Provided Saved Searches: Restrictions Saved Searches: Tags Search Templates: Quick Searches Search Templates: Views Search Templates: Sorts Shared Links System Info System Info: Languages System Info: Search Templates
Supporting Documentation
Terms of Use

Standalone FloPlan API - Obtaining Access

Since the FloPlan API operates against a standalone dataset, any existing approvals to access a RETS feed, the Spark® API, or a different RESO Web API feed will not apply. New authorization exclusive to the FloPlan API must be provided by the MLS.

Note that in most cases a developer will only need to step through the authorization process a single time for MLS wide access on behalf of their clients, however, if your IDX product is spread across multiple hosts or is not directly within your sole administrative control (such as a Wordpress Plugin), then you'll need to request multiple access tokens; one for each host/client. This requirement is for security reasons. If malicious access occurs as a result of actions by one host and FBS is forced to disable a token, this ensures that your other hosts and clients will be unaffected. If you have any questions please contact FBS at

  1. Cost
  2. The Approval Process
  3. FloPlan API Authorization Form

1. Cost

FloPlan API access is free for IDX website developers, agents, and brokers.

If you are not an IDX website developer, agent, or broker, different terms apply. Please reach out to FBS for more information.


2. The Approval Process

  1. Developer completes the FloPlan API authorization form.
  2. Developer forwards completed authorization form to the MLS (not FBS). Be sure to indicate in both the email subject and body that this is a request for the FloPlan API rather than RETS or the Spark API.
  3. The MLS will then communicate with you directly should any questions or concerns arise or sign the for if they'd like to approve your access.
  4. The MLS will forward the signed form to FBS directly.
  5. FBS will process the request and you'll receive an email at the technical contact email address noted in the authorization form containing a FloPlan API access token.

Note that most requests are processed by FBS within 24 hours; however, delays may occur. If you have not received credentials within 48 hours of the MLS confirming that they've forwarded the signed form to FBS, please contact our support team. Otherwise, all approval inquiries should be directed to the MLS.


3. FloPlan API Authorization Form

Click here and follow the steps presented on the form.