Changelog

Webhook message verification - February 2024

Now it is possible to protect your app from webhook message tampering and retransmission through signature and payload timestamp verification.

Required Migration Steps

  1. Request a webhook secret from Import2.
  2. Implement webhook message verification.

API v2.1 - February 2023

  1. Textual descriptions of import status in API responses and webhook payloads are now consistent with each other.
  2. New set of API endpoints to accept or reject sponsorship of a migration.

Required Migration Steps

  1. Update all of your API requests to use https://www.import2.com/api/v2.1 as a base URL.
  2. Make sure to update any code that depends on textual descriptions of import statuses using table of possible values.

API v2 - August 2013

API v2 includes only one significant change comparing to API v1: all imports created via API v2 start with a sample migration. Full import is scheduled only after customer expresses her desire for it. This adds one additional step into integration scenario: after the sample import is completed, customer has ability to request the full import. This could happen either by sending an e-mail to your helpdesk or by visiting a special page inside your app that explains required steps (e.g. upgrading from trial account to a paid one)

Required Migration Steps

  1. Update all of your API requests to use https://www.import2.com/api/v2 as a base URL.
  2. Let us know if you prefer your customers to pay for the full import themselves or you would like to decide which customers qualify for the free full import (i.e. you will be covering their migration costs). In case of the former, if customer decides to perform a full import, she will be ask to purchase one of the Import2 paid packages.
  3. If you have decided that you will be providing free full imports for qualifying customers, then let us know where we should direct customers requesting a full import (after customer has seen the sample is ready for full migration).