Swifty Knowledge Base

What we need to connect RealPage to your website

Updated Nov 21, 2026

The information and RealPage-side setup Swifty needs before we can connect your community's RealPage feed.

RealPage is the most common PMS we connect. Gathering this before you contact support avoids the most common delay.

  1. Confirm your RealPage site ID and PMC ID for the property.
  2. Ask RealPage to enable API access for our connection if it is not already enabled.
  3. Confirm which floor plans should show on the website are in the correct marketing floorplan group in RealPage, since plans outside that group will not appear on the site.
  4. Check your OneSite prospect settings so the leasing information matches what should be public.
  5. Tell us whether the property uses LRO, YieldStar, or AIRM revenue pricing, since that changes which rate the website shows.
  6. Send all of this to support along with your property name and site URL.
Note: once the connection is live, we map each RealPage floor plan to the matching website plan and refresh availability. If a plan is missing after launch, the most common cause is a plan sitting outside the marketing floorplan group.
Tip: if your property uses a revenue management tool such as LRO or YieldStar, check the price optimizer toggle under Settings > Integrations > RealPage after launch. This determines which price the website shows when RealPage offers more than one rate.

Still stuck?

If pricing or availability does not match RealPage after the connection is live, see the floor plan troubleshooting checklist or contact support with the floor plan name, unit number, and the price RealPage shows.

Related:

Was this article helpful?