Table of Contents

Search

  1. Preface
  2. Informatica Intelligent Cloud Services REST API
  3. Platform REST API version 2 resources
  4. Platform REST API version 3 resources
  5. Data Integration REST API
  6. Mass Ingestion Files REST API
  7. RunAJob utility
  8. REST API codes
  9. REST API resource quick references

REST API Reference

REST API Reference

Data Integration REST API

Data Integration
REST API

The REST API resources in this section apply specifically to the
Data Integration
service.
In addition to platform REST API resources, you can use the following resources when you interact with
Data Integration
through the REST API:
  • For most calls, use
    Data Integration
    REST API version 2 resources.
  • For file transfer calls, use the
    File Transfer REST API
    resources.
    File Transfer REST API
    resources include the filelistener resource and the sendfiles resource.
When you use
Data Integration
REST API version 2 resources, note the following rules:
  • Use JSON or XML format.
  • Use the serverUrl value from the login response as the base URL. For example:
    https://na4.dm-us.informaticacloud.com/saas
  • Use the following URI:
    /api/v2/<API name>
  • Use the following request header format:
    <METHOD> <serverUrl>/<URI> HTTP/<HTTP version> Content-Type: application/json Accept: application/json icSessionId: <SessionId>
In the following example, the serverUrl is
https://na4.dm-us.informaticacloud.com/saas
and the URI is
/api/v2/agent
:
<METHOD> https://na4.dm-us.informaticacloud.com/saas/api/v2/agent HTTP/1.1 Content-Type: application/json Accept: application/json icSessionId: IV4wOrJmd6YUtmKa8t
If you use a tool such as Postman that automatically includes the HTTP version, do not enter the HTTP version in the URL. If the HTTP version appears twice in the URL, the request fails.
When you use
File Transfer REST API
resources, note the following rules:
  • Use JSON format.
  • Use the following request URL:
    <serverUrl>/mftsaas/api/v1/<API name>
  • Use the following request header format:
    <METHOD> <serverUrl>/<URI> HTTP/<HTTP version> Content-Type: application/json Accept: application/json IDS-SESSION-ID: <SessionId>
    If you use a tool such as Postman that automatically includes the HTTP version, do not enter the HTTP version in the URL. If the HTTP version appears twice in the URL, the request fails.


Updated May 03, 2021