Encompass R2T to UAT Migration

Modified on Tue, Jan 27 at 10:50 AM

Client Checklist

Overview

ICE is migrating Encompass clients to the R2T UAT region (beta). As part of this migration:

  • Your existing Encompass API credentials used by Blend → Encompass will be disabled.

  • The Encompass API hostname will change from
    https://api.elliemae.com to https://concept.api.elliemae.com.

To minimize downtime and keep your Blend–Encompass integration working, we ask that you notify Blend ahead of your migration and complete the steps below.


What You Need to Do

1. Before Your Migration

  1. Confirm your current Encompass details

    • Identify your current Encompass instance ID.

    • Confirm which Encompass API user/credentials are used for the Blend integration.

  2. Notify Blend of your planned migration

    • Share with Blend Support:

      • Your planned migration date/time window.

      • Your current Encompass instance ID.

    • Confirm that Blend should obtain new R2T UAT API credentials for you.

  3. Allow time for new credentials

    • ICE typically requires 2–3 business days to issue new credentials.

    • Blend will request new credentials and prepare to update the integration in advance of your cutover.


2. After ICE Completes Your Migration to R2T UAT

  1. Confirm migration completion

    • Ensure with ICE / your internal Encompass team that your org has been fully migrated to the R2T UAT region.

    • Let Blend Support know once the migration is complete.

    • Note: The new credentials will not function until ICE finishes your migration.

  2. Update the Blend API user in Encompass

    • In Encompass, update the Blend API user (often blendApiUser or similar) with the new client ID and associated API credentials provided via Blend/ICE.

    • Save and apply the changes.

  3. Confirm with Blend that the API user is updated

    • Notify Blend Support once the API user update is complete.

    • Blend will validate the new credentials by calling the new hostname:
      https://concept.api.elliemae.com/oauth2/v1/token.


3. What Blend Will Do

Blend Support will:

  • Request and track your new R2T UAT API credentials with ICE.

  • Validate the new credentials once you complete the migration and update your Encompass API user.

  • Re-register your webhooks in the new UAT region so that Encompass events continue to flow to Blend.

  • Update Blend’s configuration to:

    • Use the new hostname https://concept.api.elliemae.com.

    • Use your new API credentials and Encompass instance ID.

You will receive confirmation from Blend when connectivity is restored and webhooks are active.


Final Client Checklist

Use this as a quick confirmation list:

  • [ ] I have provided Blend with our migration date/time and Encompass instance ID.

  • [ ] I understand that ICE will provide new API credentials for the R2T UAT region.

  • [ ] After migration, we updated our Blend API user in Encompass with the new client ID and credentials.

  • [ ] Blend confirmed:

    • [ ] The token request to https://concept.api.elliemae.com/oauth2/v1/token is successful.

    • [ ] Webhooks are re-registered and events are flowing.

  • [ ] We validated in UAT that:

    • [ ] New loans can be created in Blend and pushed to Encompass.

    • [ ] Changes in Encompass are reflected back in Blend as expected.


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article