Hi, I'm Ask INFA!
What would you like to know?
ASK INFAPreview
Please to access Ask INFA.

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

REST API Reference

REST API Reference

Lookup

Lookup

Use the lookup resource to look up an object's ID, name, path, or type attributes.

POST request

This resource is usually used to obtain an object's ID to use in an export request or job request. When you use this resource to obtain an object's ID, include the object path and type in the lookup request.
For a job request, use the value of the id field returned in the lookup response for the federated task ID field in the job request.
To request lookup information, use the following URI:
/public/core/v3/lookup
You can use the following fields in the objects object:
Field
Type
Required
Description
id
String
Required if object path and type not included.
Global unique identifier for the object.
path
String
Required with type if object ID not included.
Full path of the object including project, folder, and object name.
type
String
Required with path if object ID not included.
Type of object.
Use one of the following values:
  • PROJECT
  • FOLDER
Or use one of the following asset types:
For
Data Integration
, the object can be one of the following types:
  • DTEMPLATE. Mapping.
  • MTT. Mapping task.
  • DSS. Synchronization task.
  • DTT. Data transfer task.
  • DMASK. Masking task.
  • DRS. Replication task.
  • DMAPPLET. Mapplet created in
    Data Integration
    .
  • MAPPLET. PowerCenter mapplet.
  • CONNECTION.
  • AGENT. Secure Agent.
  • AGENTGROUP. Runtime environment.
  • BSERVICE. Business service definition.
  • HSCHEMA. Hierarchical schema.
  • PCS. PowerCenter task.
  • FWCONFIG. Fixed width configuration.
  • CUSTOMSOURCE. Saved query.
  • MI_FILE_LISTENER. File listener.
  • MI_TASK. File Ingestion and Replication.
  • DBMI_TASK. Database Ingestion and Replication
  • APPMI_TASK. Application Ingestion and Replication.
  • WORKFLOW. Linear taskflow.
  • SCHEDULE
  • SCHEDULE_JOB
  • SCHEDULE_BLACKOUT. Schedule blackout period.
  • TASKFLOW
  • UDF. User-defined function.
For
Application Integration
, the object can be one of the following types:
  • PROCESS
  • GUIDE
  • AI_CONNECTION
  • AI_SERVICE_CONNECTOR
  • PROCESS_OBJECT
For
Data Quality
, the object can be one of the following types:
  • CLEANSE
  • DEDUPLICATE
  • DICTIONARY
  • EXCEPTION
  • LABELER
  • PARSE
  • RULE_SPECIFICATION
  • VERIFIER
For B2B Gateway, the object can be one of the following types:
  • B2BGW_MONITOR
  • B2BGW_CUSTOMER
  • B2BGW_SUPPLIER
Object types are not case sensitive.

POST response

Returns object information if successful or an error object if errors occur.
If successful, returns the following lookup information for each object:
Field
Type
Description
objects
Collection
Collection of objects for which lookup is requested.
id
String
Global unique identifier for the object. Use the value of this field as the value for taskFederatedId when you submit a job request.
path
String
Full path of the object including project, folder, and object name.
type
String
Type of object.
description
String
Description of the object.
updatedBy
String
User who updated the object.
updateTime
String
Last time the object was modified.

POST example

The following example shows a lookup request for eight objects:
POST <baseApiUrl>/public/core/v3/lookup Content-Type: application/json Accept: application/json INFA-SESSION-ID: 9KA11tLGqxVcGeul8SQBK3 { "objects": [{ "id" : "2iXOKghGpySlgv6ifQImyl" }, { "path" : "Default/Synchronization Task1", "type" : "DSS" }, { "id" : "hTrrjm1kawScIm1BGEj6UV" }, { "path" : "My Project", "type" : "Project" }, { "path" : "My Project/DSS Tasks Folder", "type" : "Folder" }, { "path": "USW1R90FPZXD", "type": "Agent" }, { "path": "USW1R90FPZXD", "type": "AgentGroup" }, { "path": "FF_Conn_1", "type": "Connection" }] }
The response includes lookup information for each object as shown in the following example:
{ "objects": [ { "id": "2iXOKghGpySlgv6ifQImyl", "path": "Default/Mapping1", "type": "DTEMPLATE", "description": "My Mapping 1", "updateTime": "2018-04-13T20:44:37Z" }, { "id": "1fOqrwpFvLkimAkFFvIiwl", "path": "Default/Synchronization Task1", "type": "DSS", "description": "Sync Data Task", "updateTime": "2018-04-13T20:45:44Z" }, { "id": "hTrrjm1kawScIm1BGEj6UV", "path": "My Project/Linear Taskflow1", "type": "WORKFLOW", "description": null, "updateTime": "2018-04-13T20:50:31Z" }, { "id": "0EzsUXQ1RnkbKD6VyOukCb", "path": "My Project", "type": "Project", "description": "", "updateTime": "2018-04-13T20:40:07Z" }, { "id": "dRNcMcUVou5lh5kihmEAWl", "path": "My Project/DSS Tasks Folder", "type": "Folder", "description": "DSS Tasks", "updateTime": "2018-04-13T20:49:17Z" }, { "id": "1a8moeCNtm4fh5vGcUhxOj", "path": "USW1R90FPZXD", "type": "AGENT", "description": null, "updateTime": "2018-04-12T19:01:16Z" }, { "id": "9iJP8TdBOMujA7eH2CTm8l", "path": "USW1R90FPZXD", "type": "AgentGroup", "description": null, "updateTime": "2018-04-12T19:01:17Z" }, { "id": "5VkwOw6Jd8RglXEkxDu0ya", "path": "FF_Conn_1", "type": "Connection", "description": null, "updateTime": "2018-04-12T21:34:11Z" } ] }

0 COMMENTS

We’d like to hear from you!
Pavel Razumtsev - April 25, 2024

Please, update description for "type", as at least DBMI_TASK and APPMI_TASK are missing.

Informatica Documentation Team - April 29, 2024

Hi Pavel,

We're working to address your comment and will get back to you.

Thanks,

Informatica Documentation team 


Informatica Documentation Team - November 04, 2024

Hi Pavel,
We’re happy to let you know that we addressed your feedback in the documentation. DBMI_TASK and APPMI_TASK are included in the "type" list.
Thanks,
Informatica Documentation team


Pavel Razumtsev - October 25, 2024

Dear team,

 

the type "MAPPLET" is not correct. It is "DMAPPLET". Please, correct the page, as it makes a lot of confusion.

 

Thanks,

Pavel

Informatica Documentation Team - October 28, 2024

Hi Pavel. Thanks for your comment. DMAPPLET is the value for a mapplet created in Data Integration. MAPPLET is the value for a mapplet that was uploaded from PowerCenter. We've added the value DMAPPLET to the topic and updated the description for MAPPLET to avoid confusion. The update will be included in an upcoming release.