vREST Documentation
Space shortcuts
Page tree
Skip to end of metadata
Go to start of metadata

We are migrating our existing service to https://cloud.vrest.io which was earlier running on https://vrest.io. This guide will help you understand the impact of this migration on your testing activities.


Last Date of Migration: 12th March 2021

Brief Summary:

In your eco-system, wherever you are using the older vREST base URL which is https://vrest.io then you will need to update it to https://cloud.vrest.io. And also you will need to update our supported modules (Chrome Extension and vrunner) which were earlier connected to https://vrest.io automatically. For more details, see the section "Migration Impact" below.


As of now, both sites https://vrest.io and https://cloud.vrest.io are working in parallel. So you should be able to migrate to https://cloud.vrest.io easily without any issue. After 12th March 2021, https://vrest.io will no longer serve the vREST Cloud service. So, we recommend you migrate to https://cloud.vrest.io before that. There is no functional change in the migration process.

Migration Impact:

  1. Change in Authorization Callback:

    1. If you are using any kind of authorizations like OAuth 1.0 and/or OAuth 2.0 in your test cases then you will need to update the vREST callback URL.
    2. In your configured callback URL, replace `https://vrest.io` with `https://cloud.vrest.io`. 
      1. If your older OAuth2.0 Callback URL is
      2. Then it will be changed to the following callback URL:

  2. Change in Mock Server Base URL:

    1. If you are using vREST Mock APIs then you will need to change the Mock Server Base URL.

      1. If your older Mock Server base URL is 
        https://vrest.io/i/<instance_name>/m/<project_key>

      2. then it will be changed to the following base URL:
        https://cloud.vrest.io/i/<instance_name>/m/<project_key>

  3. Update Chrome Extension for Test Case Recording:

    1. If you are recording test cases via our chrome extension then you will need to update our chrome extension to version 1.2.9 or later.
    2. For more information, read our guide on how you may update the vREST chrome extension.

  4. Update the vrunner module for command-line execution of API tests:
    1. If you are using the vrunner module to run your API tests on the command line or with any CI/CD server, then you will need to update the vrunner module to version 0.4.4 or later.
    2. The updated vrunner module will use the new cloud vREST base URL (https://cloud.vrest.io) automatically.
    3. Also, for the command `url` option, start the URL with "https://cloud.vrest.io".


If you need any help or if you are facing any issues in this website migration then contact us at support@vrest.io.



  • No labels