Connect your first Entrata integration

For: An admin or IT admin connecting Entrata to PropSocket for the first time.

You’ll accomplish: gathering the right Entrata credentials, creating the integration, choosing which data to sync and on what schedule, and knowing what to expect from the first sync.

Entrata is the property management system (PMS) PropSocket connects to first. Once it’s connected, PropSocket pulls your properties, units, residents, and leases into a single, clean copy your team can use — and keeps it current on a schedule.

You don’t need to write code. You will need a couple of things from whoever administers your Entrata account.

---

1. Pre-flight: what to get from Entrata first

PropSocket connects to Entrata’s API with a key, so it needs read access to the data types you want to sync. Don’t reuse a person’s personal Entrata login — Entrata access for PropSocket is keyed, not username-and-password.

Ask your Entrata administrator (or Entrata support) for two things:

• An Entrata API key for PropSocket.
• Your Entrata subdomain (the short identifier for your organization’s Entrata account).

The API key needs read access to the following Entrata endpoints — one per data type PropSocket syncs:

Data type	Entrata permission
Properties	getProperties
Units	getPropertyUnits
Residents	getCustomers
Leases	getLeases

PropSocket only reads your data; it doesn’t write back to Entrata, so it never needs edit or delete permissions.

Granting the API key these permissions is done inside Entrata, not in PropSocket. If your Entrata admin needs the exact endpoint list, the table above is it — or our support team can send it; see the escalation block at the bottom.

No Entrata sandbox needed. PropSocket doesn’t connect to a separate Entrata sandbox. If you want to try things out first, use PropSocket’s Test Mode (step 3), which runs the integration in isolation on your side without committing it to your live data flow.

2. Find your credentials

Once the API key exists, you’ll enter two values into PropSocket:

• API key — the key from step 1.
• Subdomain — your Entrata subdomain.

Keep these handy and private for the next step. Don’t email them around.

3. Create the integration in PropSocket

Creating an Entrata integration is a short, three-step wizard. This is the first step.

1. In the dashboard, start a new integration.
2. Give it a Name, choose Entrata as the PMS Type, and pick an Environment:
   • Production — connects to your real, live Entrata data.
   • Test Mode — runs the integration in isolation so you can validate the setup before going live.
3. Optionally add Tags to organize the integration by team, region, or portfolio.
4. Under Credentials, enter your API key and Subdomain. PropSocket encrypts the key as soon as you save and never shows it again on screen. (There’s an optional Base URL — leave it blank unless Entrata gave you a custom endpoint.)
5. Click Next: Select Services.

You don’t need to run a separate “test connection” step. When you click Next: Select Services, PropSocket tests your credentials against Entrata for you. If something’s wrong, it tells you right there — the most common causes:

• Wrong or expired API key — double-check the key and that it’s the one issued for PropSocket.
• Wrong subdomain — confirm the subdomain matches your Entrata account.
• Permissions too narrow — the key works but can’t read one of the data types. Go back to step 1 and confirm the endpoint permissions in the table.

Both admins and members can create an integration, so you don’t need to be an admin for this step.

4. Select which data to sync

Once your credentials check out, PropSocket shows the data services available for Entrata: Properties, Units, Residents, and Leases.

• Check the ones you want PropSocket to sync.
• If a service is greyed out and marked “(not available for your API key)”, your Entrata key doesn’t have permission for that data type yet. Go back to step 1 and grant the matching endpoint from the table.

Click Next: Schedule when you’ve made your selections.

5. Set your sync schedule

The last step controls how often PropSocket syncs and how gently it calls Entrata:

• Sync frequency — how often PropSocket checks Entrata for changes. Every 12 hours is a good starting point.
• Require property approval — optionally hold newly discovered properties for manual approval before they sync. Turn this on if you want to control which properties land in PropSocket.

Click Create Integration to finish. PropSocket saves the integration and queues the first sync.

6. What to expect from the first sync

When the integration is created and enabled, PropSocket runs an initial sync — a one-time bulk load of all your existing Entrata data.

What to expect:

• It can take a while. The first sync pulls everything, so the time depends on how many properties, units, residents, and leases you have. Larger portfolios take longer.
• Watch for “first sync complete.” When the initial load finishes, PropSocket records a FIRST_SYNC_COMPLETE event. That’s your signal the data is loaded and ready.
• No flood of change notifications. If your team set up webhooks, the first sync does not fire individual “new record” or “updated record” webhooks — that would be thousands of notifications at once. Those only start with later, ongoing syncs. After the first sync completes, your data is available in the dashboard and through the API.

After the initial sync, PropSocket switches to ongoing syncs on the schedule you set in step 5. From then on, it only moves what changed.

---

If this didn’t work

If credentials keep getting rejected, or the first sync doesn’t complete, don’t keep retrying blindly — send us the details and we’ll pinpoint it.

Open a support ticket by emailing support@propsocket.io and include:

• Organization slug (the short name in your dashboard URL, e.g. acme-residential)
• Integration Name (shown on the integration’s page)
• Whether you’re on Production or Test Mode
• What you expected (e.g., “credentials should pass”)
• What you saw (the exact error message or status)
• A screenshot of the error

Please do not paste your raw Entrata API key into a ticket. We never need your credentials to investigate, and our team will never ask for them.