API: Basic Migration Overview

Migrating your SafeToSend real-time API account from the legacy FreshAddress client portal to the InstantData client portal is simple and will be performed by AtData's Client Services team. The cutover will be transparent and will not incur any downtime. For most clients, no development is required since API requests and responses will remain the same, and no new validation codes are introduced.

Domain/URL

There will be no change to the domain name or request URL.

Response Format

There will be no change to the response format.

SSL/TLS

There will be no change to the SSL certificate, minimum TLS level (TLS 1.2), or TLS cipher list.

HTTP response header

Basic requests:

Once your account is migrated, our API will return content-type, content-length, and server headers that are not present in the pre-migration API:

content-type: text/plain
content-length: 296
server: Jetty(12.0.13)

With &cth=true

If your requests contain "&cth=true", the only change you'll only see is a casing change in the content-type header, plus content-length and server headers that are not present in the pre-migration API:

Old:

content-type: application/json;charset=UTF-8

New:

content-type: application/json;charset=utf-8
content-length: 296
server: Jetty(12.0.13)

Flag parameters in the URL

Please see https://docs.atdata.com/docs/api-request-flags for information on flag parameters in the request URL that can modify the behavior of the API.