REST V2 Connector Guide > REST V2 Operations > Rules and Guidelines for REST V2 Operations

Rules and Guidelines for REST V2 Operations

Consider the following rules and guidelines for REST V2 Operations:

•If you want to connect to a web service that uses OAUTH version 2.0, provide the values of authentication details as custom header fields or query parameters in a request message.
•REST V2 Connector does not extract header details from the response message.
•Elements related to header fields, path parameters, and query parameters appears as input fields in Source, Target, and Midstream transformation.
•REST V2 Connector does not support a proxy server on which authentication is enabled.
•REST V2 Connector supports only Integer and Decimal data types.
•REST V2 Connector supports packed field in Source transformation only.
•REST V2 Connector supports simple file upload.
•REST V2 Connector overrides the Content-Type and Accept headers.
•You must not create in-out parameters for advanced properties, such as Page Parameter, Start Page, End Page, and Override URL.
•You cannot run a task on Hosted Agent if the REST API is HTTPS enabled.
•If the swagger URL you specify is not accessible or the proxy server is not accessible, mappings fail and one of the following errors is logged in the session log. The behavior is same for the source, midstream, and target mappings.

- [ERROR] com.informatica.sdk.helper.common.ApiException: java.net.UnknownHostException: inv28pers108Communication exception, Proxy settings might be incorrect.
- [ERROR] com.informatica.sdk.helper.common.ApiException: java.net.ConnectException: Connection refused: connectCommunication exception, Proxy settings might be incorrect.