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. Mass Ingestion Streaming REST API
  8. RunAJob utility
  9. ParamSetCli utility
  10. REST API codes
  11. REST API resource quick references

REST API Reference

REST API Reference

Dynamic mapping tasks

Dynamic mapping tasks

You can create a dynamic mapping task with the REST API to batch jobs together that are based on the same mapping. You can also run the task and get details about the job.
Use the following resources for dynamic mapping tasks:
  • Login. Use to log in to
    Informatica Intelligent Cloud Services
    and get the session ID to use in dynamic task REST API calls.
  • dynamictask. Use to create, view, update, or delete a dynamic mapping task.
  • job. Use to start, stop, or get details about a dynamic mapping task run instance.
When you use these resources, note the following rules:
  • Use JSON format.
  • Use the following URL:
    <serverUrl>/batch-mapping/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>
    The server URL includes the name and region of the POD that your organization uses and the
    Informatica Intelligent Cloud Services
    domain, informaticacloud.com. If you do not know the name and region of your organization's POD, you can find it by logging in to
    Informatica Intelligent Cloud Services
    through the user interface. The POD information is located in the browser's address bar.
    In the following example, https://na1.dm-us.informaticacloud.com is the server URL:
    https://na1.dm-us.informaticacloud.com/diUI/products/integrationDesign/main/home
    Use the server URL as the base URL in the header of REST API calls.
    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.

0 COMMENTS

We’d like to hear from you!