FEATURE: Customer-Level Entrata API token

Last updated: October 29, 2026

For most customers, the same Entrata API token is used across all integrations. Previously, Propexo required the API token to be uploaded at the integration level, meaning that whenever the token needed to be updated, you had to update it separately on every Entrata integration.

With this change, you can now store an Entrata API token at the customer level. When setting up a new integration, you can either:

  • Use the customer-level API token, which will update automatically across all integrations whenever you change it at the customer level, or

  • Continue setting the API token at the integration level, if that better fits your workflow

Storing the token in one place means that when it’s reissued or rotated, you only need to update it once, instead of editing every integration individually.

Do I have to do anything?

No. This change is fully backward compatible:

  • Existing integrations with an API token already set will keep using that token, unchanged, until it’s removed. If you’d like us to migrate all of your Entrata integrations to a customer-level token, you can file a support request.

  • New integrations can still use an integration-level token if you prefer, or you can set the token once at the customer level and select it during setup.

  • Nothing about your existing API requests or flows needs to change.

To update your credential at the customer level, go to the Integrations panel and select the PMS you’re connecting to.

A banner will appear with the option to set the customer-level credential. From there, you can switch each integration to the customer-level token individually, or contact support and we’ll move them all over in bulk.