Entrata API key rotation and your Propexo integrations

Last updated: August 24, 2026

Entrata rotates your API key once a year and gives you 30 days to move to the new one. In Propexo, that key has to be replaced on every Entrata integration using it — either one at a time in the dashboard or in bulk through the configuration API.

What Entrata is doing

This is Entrata's policy, applied across their platform. Nothing in this section is specific to Propexo.

On August 20, 2026, Entrata announced that it now rotates every API key annually, effective immediately.

What rotates

The master API key Entrata issued you when you were approved. Any key already older than a year is first in line.

Timing

You receive the new key 30 days before the current one is deactivated. Both work during that window.

Notices

Entrata emails the contact on your Entrata account twice: once when the new key is generated, and again 7 days before the old one expires.

Why

Entrata's broader API security initiative. Annual rotation is standard for long-lived credentials.

Entrata owns this policy and its schedule. For your own rotation dates, contact apisupport@entrata.com.

What that means inside Propexo

Each Entrata integration in Propexo authenticates using the API key saved in that integration's settings, and Propexo does not receive key updates automatically.

One key, potentially many integrations. If the expired key is used by more than one Entrata integration, every one of them needs the new key. Any integration still presenting the old key after it is deactivated returns authentication errors and stops pulling data.

What a stale key looks like

Entrata's two emails are your advance notice, so they are the signal to watch for rather than anything in the Propexo dashboard. Make sure they reach whoever administers your integrations.

Once the old key is deactivated, an integration still using it returns authentication errors instead of data, which in practice shows up as a sync that stops returning records. That can read as a quiet day rather than a problem — which is why both methods below end with confirming records are flowing, and why it's worth updating early in the 30-day window while the old key is still there to fall back on.

Updating one integration

  1. Open the Entrata integration in your Propexo dashboard, click the action button in the top-right corner, then Edit credentials.

  2. Enter the new API key from Entrata in the corresponding field.

  3. Leave other fields blank.

  4. Save, then confirm records are syncing.

Updating all of them at once

If the key is used by more than a handful of integrations, do this through the configuration API rather than by hand:

  1. Pull all of your integrations

  2. Filter the response to your Entrata integrations

  3. Push the new key to each one

  4. Re-pull the list and confirm every Entrata integration now carries the new key, then confirm records are flowing

Update within a week of receiving the new key, not on day 29. That leaves room to confirm records are flowing and fall back to the old key while it's still valid.

Propexo does not need a copy of your key. You enter it in your own dashboard or push it through the API. Please do not send an API key by email, Slack, or a support ticket.

Troubleshooting

  • An Entrata integration stopped returning records: A rotated key is the most likely cause if the integration had been running fine. Confirm whether Entrata issued a new key for your account in the last 30 days, then update the credential. If nobody can find the rotation email, apisupport@entrata.com can confirm your key's status.

  • Some integrations work and others do not: Expected if the key was updated on some but not all of them. Pull your integration list through the configuration API and check every Entrata integration against the new key rather than working from memory.

  • Where will I see that my key is about to expire? In Entrata's two emails, which are the authoritative notice since Entrata owns the rotation schedule. Expiry dates are not surfaced in the Propexo dashboard, so those emails are the thing to watch — and it's worth confirming who on your side receives them.

  • Who receives Entrata's rotation emails? The contact on your Entrata account, which is often not the person who administers your Propexo integrations. Worth settling before a rotation lands, because the 30-day clock runs whether or not anyone is watching that inbox. apisupport@entrata.com can confirm who it is.

  • Can Propexo update the key for me? No. The key goes from Entrata straight into your own dashboard or API call, so it never passes through an email or a support ticket.

Questions

Anything about your integrations, or confirming data is flowing after an update: support@propexo.com Anything about the policy, your rotation schedule, or a key you did not receive: apisupport@entrata.com