When you log in to an Informatica Intelligent Cloud Services organization using the REST API, the login resource returns the REST API session ID. You include this session ID in most subsequent REST API requests during the session. The session ID expires after 30 minutes of inactivity. A grace period of up to 2 minutes might be included to account for any network or unexpected delays.
You can use the same session ID for version 2 and version 3 resources. For example, if you log in using the version 2 login resource, you can use the session ID that was returned in the login response in a request that uses a version 3 resource.
To make a call that uses a REST API version 2 resource, use the icSessionId attribute to include the session ID in the header. To make a call that uses a REST API version 3 resource, use the INFA-SESSION-ID attribute to include the session ID in the header.
The following example shows how icSessionId is used in the header for a REST API version 2 call::
GET https://app.informaticacloud.com/saas/api/v2/licenseInfo/org/<id> Content-Type: application/xml Accept: application/xml icSessionId: IV4wOrJmd6YUtmKa8t
The following example shows how INFA-SESSION-ID is used in the header for a REST API version 3 call:
GET https://app.informaticacloud.com/saas/public/core/v3/license/org/{orgId} Content-Type: application/json Accept: application/json INFA-SESSION-ID: 9KA11tLGqxVcGeul8SQBK3
You can submit a POST request to determine the status of a session ID. Use the following URI to submit the request:
/api/v2/user/validSessionId
Include the following attributes in the request:
•userName. Your Informatica Intelligent Cloud Services user name.
•icToken. The session ID.
For example, you might use the following request:
POST https://app.informaticacloud.com/saas/api/v2/user/validSessionId Content-Type: application/json Accept: application/json
The response returns whether the session ID is valid or not and the number of minutes left before the session ID expires. For example, you might receive the following response:
Note: The timeUntilExpire value changes to "0" when the session will expire in less than 1 minute. The isValidToken value changes to "false" when the session expires. To avoid the risk of authentication failure, reauthenticate when the timeUntilExpire value changes to 0.