Getting Started with Cloud Data Profiling REST API

Back Next

REST API Versions

Informatica Intelligent Cloud Services supports the platform REST API version 2 and version 3 resources, and service-specific resources.

You can log in to Informatica Intelligent Cloud Services using the platform REST API version 2 or version 3 login resource. The version of any subsequent resource that you use does not need to match the version of the login resource that you use to log in.

The following are differences between REST API version 2 and version 3 calls:

Format: You can use the following formats depending upon which API version you use:

Version 2 supports XML and JSON calls.
Version 3 supports JSON calls.

Login URL: Use one of the following login URLs:

For version 2, use: https://dm-{POD_region}.informaticacloud.com/ma/api/v2/user/login
For version 3, use: https://dm-{POD_region}.informaticacloud.com/saas/public/core/v3/login

Your POD (Point of Deployment) region is based on the location of your Informatica Intelligent Cloud Services data center. Use one of the following POD regions:

For North America, use us.
For Europe, use eu.
For Asia, use ap.

The POD region is included in the URL you receive when you register with Informatica Intelligent Cloud Services.

Base URL: The login response includes the base URL that you must include in subsequent calls. The name of the base URL attribute that is included in the response depends on the API version that you use to log in, for example:

In a version 2 response, the attribute name is serverUrl.
In a version 3 response, the attribute name is baseApiUrl.

The base URL includes the POD that your organization uses. In the following example, the POD is usw3:
https://usw3.dm-us.informaticacloud.com/saas/public/core/v3/login

Request URL: The URL that you use in requests differs between the version 2 and version 3 resources, for example:

For version 2 resources, use <SERVERUR>/api/v2/.
For version 3 resources, use <BASEAPIURL>/public/core/v3/.

Session ID: The login response includes a session ID that you must include in headers during the session. You can use the same session ID for version 2 and version 3 resources. The name of the attribute for session ID in the login response depends on the API version that you use to log in. Use one of the following attributes:

For version 2 resources, use IDS-SESSION-ID in the header.
For version 3 resources, use INFA-SESSION-ID in the header.