RealPage Exchange API
✓ Official Vendor SpecCRMCustomer SupportapiKey, basic14 EndpointsREST
For Agents
Programmatically list residents, get resident details. Covers 14 operations with apiKey, basic authentication.
Use for: I need to residents, I want to resident details, Search for resident events, Find all leases
Not supported: Does not handle payments, communications, or developer tools — use for crm only.
The RealPage Exchange (RPX) API enables integration with RealPage's property management platform. The API provides access to resident management, lease tracking, property operations, and financial data. Access requires an active RealPage partner agreement through the RPX AppPartner Program. The API supports both REST and SOAP interfaces; this specification covers the REST API endpoints. The API exposes 14 endpoints secured with apiKey, basic authentication.
Install Jentic One Beta
Connect the RealPage Exchange API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the RealPage Exchange 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.
1
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 | sh2
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 instanceJentic 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 RealPage Exchange API.
List residents
Get resident details
Access RealPage Exchange API crm resources via REST API
Use Cases
Patterns agents use RealPage Exchange API for, with concrete tasks.
★ CRM Operations
Use the RealPage Exchange API to perform crm operations programmatically. The API provides 14 endpoints covering core functionality including list residents, get resident details, get resident events.
Call GET /residents to list residents
Automated Residents Management
Automate residents operations by combining multiple RealPage Exchange API endpoints. Agents can get resident details and then get resident events in a single workflow.
Call GET /residents/{residentId} to get resident details, then verify the result
AI Agent Integration via Jentic
AI agents discover and call RealPage Exchange 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 apiKey, basic tokens manually.
Search Jentic for 'list residents', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
14 endpoints — the realpage exchange (rpx) api enables integration with realpage's property management platform.
METHOD
PATH
DESCRIPTION
GET
/residents
List residents
GET
/residents/{residentId}
Get resident details
GET
/residents/events
Get resident events
GET
/leases
List leases
GET
/leases/{leaseId}
Get lease details
GET
/sites
List sites
GET
/sites/{siteId}
Get site details
GET
/sites/{siteId}/units
List units for a site
GET
/residents
List residents
GET
/residents/{residentId}
Get resident details
GET
/residents/events
Get resident events
GET
/leases
List leases
GET
/leases/{leaseId}
Get lease details
GET
/sites
List sites
GET
/sites/{siteId}
Get site details
GET
/sites/{siteId}/units
List units for a site
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
RealPage Exchange API apiKey, basic 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 residents') and Jentic returns the matching RealPage Exchange API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct RealPage Exchange 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.
FAQs
Specific to using RealPage Exchange API through Jentic.
What authentication does the RealPage Exchange API use?
The RealPage Exchange API uses apiKey, basic authentication. 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 residents with the RealPage Exchange API?
Yes. Use the GET /residents endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the RealPage Exchange 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 residents through Jentic?
Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'list residents'. Jentic returns the matching RealPage Exchange API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.
How many endpoints does the RealPage Exchange API have?
The RealPage Exchange API exposes 14 endpoints covering residents, leases, sites operations.
GET STARTED