JSON and XML Response Examples

On the General Information tab:

1. In the Operation Name field, enter Test Connection (JSON) as the operation name.
2. From the Operation Type dropdown list, select Test Connection.
3. In the Context URL field, enter the URL specific to the test connection.
4. In the HTTP Method dropdown list, select POST.

On the Header and Body tab:

The Header has the data keys and their corresponding values. These key value pairs are sent as part of the header in the HTTP request.

The HTTP body is used for posting the data with a request. The body has two data entry types, Form Data and Raw. You can use either of them for a test connection.

In the Raw field, enter the JSON payload for the test connection.

On the Response Information tab:

The Root Path is the common path present in the JSON response. The Success Code is the successful HTTP response code expected by the respective Web Service operation. By default, the success code is 2**.

On the Response Mapping tab:

Below is an example of a schema that is mapped to JSON response. Refer to Configuration for Response for more information.

On the General Information tab:

1. In the Operation Name field, enter Account Aggregation - 1 (JSON) as the operation name.
2. From the Operation Type dropdown list, select Account Aggregation.
3. In the Context URL field, enter the URL specific to the account aggregation.
4. In the HTTP Method dropdown list, select POST.

On the Header and Body tab:

The Header has the data keys and their corresponding values. These key value pairs will be sent as part of the Header in the HTTP Request.

The HTTP body is used for posting the data with a request. The body has two data entry types, Form Data and Raw. You can use either of them for an account aggregation.

In the Raw field, enter the JSON payload for the account aggregation.

On the Response Information tab:

The Root Path is the common path present in the JSON response. The Success Code is the successful HTTP response code expected by the respective Web Service operation. By default, the success code is 2**.

On the Response Mapping tab:

Refer to Configuration for Response for more information about the raw JSON response on which the Response Information schema is mapped.

On the General Information tab:

1. In the Operation Name field, enter Account Aggregation - 2 (JSON) as the operation name.
2. From the Operation Type dropdown list, select Account Aggregation.
3. In the Context URL field, enter the URL specific to the account aggregation.
4. In the HTTP Method dropdown list, select POST.

On the Header and Body tab:

The Header has the data keys and their corresponding values. These key value pairs will be sent as part of the Header in the HTTP Request.

The HTTP body is used for posting the data with a request. The body has two data entry types, Form Data and Raw. You can use either of them for an account aggregation.

In the Raw field, enter the JSON payload for the account aggregation.

To fetch additional attributes from another endpoint, use the id (identity attribute) from the previous response. Add these attributes in Schema Attribute section of Response Mapping of the first end point (Account Aggregation - 1).

In the following screenshot, $response.team_member_id$ represents the identity that was aggregated in the Account Aggregation-1 and is mentioned previously in the schema mapping section of Account Aggregation -1.

On the Response Information tab:

The Root Path is the common path present in the JSON response. The Success Code is the successful HTTP response code expected by the respective Web Service operation. By default, the success code is 2**.

On the Response Mapping tab:

Below is an example of a schema that is mapped to XML response. Refer to Configuration for Response for more information.

On the Parent Endpoint tab:

In the following example, Account Aggregation -1 (JSON) is the parent endpoint and Account Aggregation - 2(JSON) is its child endpoint.

From the Parent Endpoint Name dropdown list, select Account Aggregation - 1 (JSON), as shown below.

On the General Information tab:

1. In the Operation Name field, enter Account Aggregation (GraphQL).
2. From the Operation Type dropdown list, select Account Aggregation.
3. In the Request Type field, select GraphQL.
4. In the Query and GraphQL Variables sections, enter the query and variables specific to the account aggregation.

On the Header tab:

The Header has the data keys and their corresponding values. These key value pairs will be sent as part of the Header in the HTTP Request.

On the Response Information tab:

The Root Path is the common path present in the JSON response. The Success Code are the successful HTTP response codes expected by the respective Web Service operation. By default, the success code is 2**.

On the Response Mapping tab:

Enter the Schema Attribute and Attribute Path for JSON response. Refer to Configuration for Response for more information.

On the XPath Namespace Mapping tab:

Enter the Namespace Prefix and Namespace URL for JSON response.

On the Parent Endpoint tab:

From the Parent Endpoint dropdown list, select Account Aggregation(GraphQL).

On the Paging tab:

Enter the cursor-based pagination values.

On the General Information tab:

1. In the Operation Name field, enter Create Account (JSON) as the operation name.
2. From the Operation Type dropdown list, select Create Account.
3. In the Context URL field, enter the URL specific to the create account operation.
4. In the HTTP Method dropdown list, select POST.

On the Header and Body tab:

The Header has the data keys and their corresponding values. These key value pairs will be sent as part of the Header in the HTTP Request.

The HTTP body is used for posting the data with a request. The body has two data entry types, Form Data and Raw. You can use either of them for account creation.

In the Raw field, enter the JSON payload for the account creation.

In the following screenshot, the $plan keyword represents the provisioning plan that is passed to the provision method. For example, $plan.member_email$ checks for the email in the attribute request and updates in the body after it is found.

On the Response Information tab:

The Root Path is the common path present in the JSON response. The Success Code is the successful HTTP response code expected by the respective Web Service operation. By default, the success code is 2**.

On the Response Mapping tab:

Refer to Configuration for Response for more information about the raw JSON response on which the Response Information schema is mapped.

On the General Information tab:

1. In the Operation Name field, enter Create Account(GraphQL) as the operation name.
2. From the Operation Type dropdown list, select Create Account.
3. In the Request Type field, select GraphQL.
4. Enter the Query and GraphQL Variables specific to the account aggregation.

On the Header and Body tab:

The Header has the data keys and their corresponding values. These key value pairs will be sent as part of the Header in the HTTP Request.

On the Response Information tab:

The Root Path is the common path present in the JSON response. The Success Code is the successful HTTP response code expected by the respective Web Service operation. By default, the success code is 2**.

On the Response Mapping tab:

The following is an example of a schema that is mapped to the JSON response. For more information, refer to to Configuration for Response.

On the XPath Namespace Mapping tab:

Enter the Namespace Prefix and Namespace URL for JSON response.

On the General Information tab:

1. In the Operation Name field, enter Add Entitlement (JSON) as the operation name.
2. From the Operation Type dropdown list, select Add Entitlement.
3. In the Context URL field, enter the URL specific to the entitlement.
4. In the HTTP Method dropdown list, select POST.

On the Header and Body tab:

The Header has the data keys and their corresponding values. These key value pairs will be sent as part of the Header in the HTTP Request.

The HTTP body is used for posting the data with a request. The body has two data entry types, Form Data and Raw. You can use either of them for adding entitlements.

In the Raw field, enter the JSON payload for the entitlement.

In the following screenshot, the plan.nativeIdentity keyword signifies the AccountID (identity attribute) in the account request of the plan. If the plan contains the identity attribute of an account, it can be updated in the payload with $plan.nativeIdentity$.

On the Response Information tab:

The Root Path is the common path present in the JSON response. The Success Code is the successful HTTP response code expected by the respective Web Service operation. By default, the success code is 2**.

On the Response Mapping tab:

Refer to Configuration for Response for more information about the raw JSON response on which the Response Information schema is mapped.

On the General Information tab:

1. In the Operation Name field, enter Remove Entitlement (JSON) as the operation name.
2. From the Operation Type dropdown list, select Remove Entitlement.
3. In the Context URL field, enter the URL specific to the entitlement.
4. In the HTTP Method dropdown list, select POST.

On the Header and Body tab:

The Header has the data keys and their corresponding values. These key value pairs will be sent as part of the Header in the HTTP Request.

The HTTP body is used for posting the data with a request. The body has two data entry types, Form Data and Raw. You can use either of them for removing entitlements.

In the Raw field, enter the JSON payload for the entitlement.

In the following screenshot, the plan.nativeIdentity keyword signifies the AccountID (identity attribute) in the account request of the plan. If the plan contains the identity attribute of an account, it can be updated in the payload with $plan.nativeIdentity$.

On the Response Information tab:

The Root Path is the common path present in the JSON response. The Success Code is the successful HTTP response code expected by the respective Web Service operation. By default, the success code is 2**.

On the Response Mapping tab:

Refer to Configuration for Response for more information about the raw JSON response on which the Response Information schema is mapped.

On the General Information tab:

1. In the Operation Name field, enter Update Account (JSON) as the operation name.
2. From the Operation Type dropdown list, select Update Account.
3. In the Context URL field, enter the URL specific to the account.
4. In the HTTP Method dropdown list, select POST.

On the Header and Body tab:

The Header has the data keys and their corresponding values. These key value pairs will be sent as part of the Header in the HTTP Request.

The HTTP body is used for posting the data with a request. The body has two data entry types, Form Data and Raw. You can use either of them for updating accounts.

In the Raw field, enter the JSON payload for the account.

On the Response Information tab:

The Root Path is the common path present in the JSON response. The Success Code is the successful HTTP response code expected by the respective Web Service operation. By default, the success code is 2**.

On the Response Mapping tab:

Refer to Configuration for Response for more information about the raw JSON response on which the Response Information schema is mapped.

On the General Information tab:

1. In the Operation Name field, enter Get Object (JSON) as the operation name.
2. From the Operation Type dropdown list, select Get Object.
3. In the Context URL field, enter the URL specific to the get object.
4. In the HTTP Method dropdown list, select POST.

On the Header and Body tab:

The Header has the data keys and their corresponding values. These key value pairs will be sent as part of the Header in the HTTP Request.

The HTTP body is used for posting the data with a request. The body has two data entry types, Form Data and Raw. You can use either of them for get object.

In the Raw field, enter the JSON payload for get object.

In the following screenshot, the $nativeIdentity$ signifies the AccountID (identity attribute) in the plan or during getObject operation. For example, nativeIdentity is used along with the keyword as follows:

getobject: $getObject.nativeIdentity$

This $nativeIdentity$ can be used in the Authentication URL.

On the Response Information tab:

The Root Path is the common path present in the JSON response. The Success Code is the successful HTTP response code expected by the respective Web Service operation. By default, the success code is 2**.

On the Response Mapping tab:

Refer to Configuration for Response for more information about the raw JSON response on which the Response Information schema is mapped.

On the General Information tab:

1. In the Operation Name field, enter Enable Account - 1 (JSON) as the operation name.
2. From the Operation Type dropdown list, select Enable Account.
3. In the Context URL field, enter the URL specific to the account.
4. In the HTTP Method dropdown list, select POST.

On the Header and Body tab:

The Header has the data keys and their corresponding values. These key value pairs will be sent as part of the Header in the HTTP Request.

The HTTP body is used for posting the data with a request. The body has two data entry types, Form Data and Raw. You can use either of them for enabling an account.

In the Raw field, enter the JSON payload for the account.

On the Response Information tab:

The Root Path is the common path present in the JSON response. The Success Code is the successful HTTP response code expected by the respective Web Service operation. By default, the success code is 2**.

On the Response Mapping tab:

Refer to Configuration for Response for more information about the raw JSON response on which the Response Information schema is mapped.

On the General Information tab:

1. In the Operation Name field, enter Enable Account - 2 (JSON) as the operation name.
2. From the Operation Type dropdown list, select Enable Account.
3. In the Context URL field, enter the URL specific to the account.
4. In the HTTP Method dropdown list, select POST.

On the Header and Body tab:

The Header has the data keys and their corresponding values. These key value pairs will be sent as part of the Header in the HTTP Request.

The HTTP body is used for posting the data with a request. The body has two data entry types, Form Data and Raw. You can use either of them for enabling an account.

In the Raw field, enter the JSON payload for the account.

On the Response Information tab:

The Root Path is the common path present in the JSON response. The Success Code is the successful HTTP response code expected by the respective Web Service operation. By default, the success code is 2**.

On the General Information tab:

1. In the Operation Name field, enter Disable Account - 1 (JSON) as the operation name.
2. From the Operation Type dropdown list, select Disable Account.
3. In the Context URL field, enter the URL specific to the account.
4. In the HTTP Method dropdown list, select POST.

On the Header and Body tab:

The Header has the data keys and their corresponding values. These key value pairs will be sent as part of the Header in the HTTP Request.

The HTTP body is used for posting the data with a request. The body has two data entry types, Form Data and Raw. You can use either of them for disabling an account.

In the Raw field, enter the JSON payload for the account.

On the Response Information tab:

The Root Path is the common path present in the JSON response. The Success Code is the successful HTTP response code expected by the respective Web Service operation. By default, the success code is 2**.

On the Response Mapping tab:

Refer to Configuration for Response for more information about the raw JSON response on which the Response Information schema is mapped.

On the General Information tab:

1. In the Operation Name field, enter Disable Account - 2 (JSON) as the operation name.
2. From the Operation Type dropdown list, select Disable Account.
3. In the Context URL field, enter the URL specific to the account.
4. In the HTTP Method dropdown list, select POST.

On the Header and Body tab:

The Header has the data keys and their corresponding values. These key value pairs will be sent as part of the Header in the HTTP Request.

The HTTP body is used for posting the data with a request. The body has two data entry types, Form Data and Raw. You can use either of them for disabling an account.

In the Raw field, enter the JSON payload for the account.

On the Response Information tab:

The Root Path is the common path present in the JSON response. The Success Code is the successful HTTP response code expected by the respective Web Service operation. By default, the success code is 2**.

On the General Information tab:

1. In the Operation Name field, enter Change Password (JSON) as the operation name.
2. From the Operation Type dropdown list, select Chance Password.
3. In the Context URL field, enter the URL specific to the change password operation.
4. In the HTTP Method dropdown list, select POST.

On the Header and Body tab:

The Header has the data keys and their corresponding values. These key value pairs will be sent as part of the Header in the HTTP Request.

The HTTP body is used for posting the data with a request. The body has two data entry types, Form Data and Raw. You can use either of them for changing a password.

In the Raw field, enter the JSON payload for the password change.

On the Response Information tab:

The Root Path is the common path present in the JSON response. The Success Code is the successful HTTP response code expected by the respective Web Service operation. By default, the success code is 2**.

On the General Information tab:

1. In the Operation Name field, enter Test Connection (XML) as the operation name.
2. From the Operation Type dropdown list, select Test Connection.
3. In the Context URL field, enter the URL specific to the test connection.
4. In the HTTP Method dropdown list, select POST.

On the Header and Body tab:

The Header has the data keys and their corresponding values. These key value pairs are sent as part of header in the HTTP request.

The HTTP body is used for posting the data with a request. The body has two data entry types, Form Data and Raw. The XML format does not support Form Data.

In the Raw field, enter the XML payload for the test connection.

On the Response Information tab:

The Root Path is the common path present in the XML response. The Success Code is the successful HTTP response code expected by the respective Web Service operation. By default, the success code is 2**.

On the General Information tab:

1. In the Operation Name field, enter Account Aggregation - 1 (XML) as the operation name.
2. From the Operation Type dropdown list, select Account Aggregation.
3. In the Context URL field, enter the URL specific to the account aggregation.
4. In the HTTP Method dropdown list, select POST.

On the Header and Body tab:

The Header has the data keys and their corresponding values. These key value pairs will be sent as part of the Header in the HTTP Request.

The HTTP body is used for posting the data with a request. The body has two data entry types, Form Data and Raw. The XML format does not support Form Data.

In the Raw field, enter the XML payload for the account aggregation.

On the Response Information tab:

The Root Path is the common path present in the XML response. The Success Code is the successful HTTP response code expected by the respective Web Service operation. By default, the success code is 2**.

On the Response Mapping tab:

Below is an example of a schema that is mapped to XML response. Refer to Configuration for Response for more information.

On the XPath Namespace Mapping tab:

The namespace xmlns is the default namespace for the example mentioned in this section, and it is represented as ns in the following screenshot.

On the General Information tab:

1. In the Operation Name field, enter Account Aggregation - 2 (XML) as the operation name.
2. From the Operation Type dropdown list, select Account Aggregation.
3. In the Context URL field, enter the URL specific to the account aggregation.
4. In the HTTP Method dropdown list, select POST.

On the Header and Body tab:

The Header has the data keys and their corresponding values. These key value pairs will be sent as part of the Header in the HTTP Request.

The HTTP body is used for posting the data with a request. The body has two data entry types, Form Data and Raw. The XML format does not support Form Data.

In the Raw field, enter the XML payload for the account aggregation.

To fetch additional attributes from another endpoint, use the id (identity attribute) from the previous response. Add these attributes in Schema Attribute section of Response Mapping of the first end point (Account Aggregation - 1).

In the following screenshot the $response.team_member_id$ represents the identity that was aggregated in Account Aggregation-1 and mentioned in the schema mapping section of Account Aggregation -1.

On the Response Information tab:

The Root Path is the common path present in the XML response. The Success Code is the successful HTTP response code expected by the respective Web Service operation. By default, the success code is 2**.

On the Response Mapping tab:

Below is an example of a schema that is mapped to XML response. Refer to Configuration for Response for more information.

On the XPath Namespace Mapping tab:

The namespace xmlns is the default namespace for the example mentioned in this section, and it is represented as ns in the following screenshot.

On the Parent Endpoint tab:

In the following example, Account Aggregation -1 (JSON) is the parent endpoint and Account Aggregation - 2(JSON) is its child endpoint.

From the Parent Endpoint Name dropdown list, select Account Aggregation - 1 (JSON), as shown below.

On the General Information tab:

1. In the Operation Name field, enter Create Account (XML) as the operation name.
2. From the Operation Type dropdown list, select Create Account.
3. In the Context URL field, enter the URL specific to the account creation.
4. In the HTTP Method dropdown list, select POST.

On the Header and Body tab:

The Header has the data keys and their corresponding values. These key value pairs will be sent as part of the Header in the HTTP Request.

The HTTP body is used for posting the data with a request. The body has two data entry types, Form Data and Raw. The XML format does not support Form Data.

In the Raw field, enter the XML payload for the account creation.

In the following screenshot, the $plan keyword represents the Provisioning Plan that is passed to the provision method. For example, $plan.LastName checks for the last name in the attribute request and updates in the body after it is found.

On the Response Information tab:

The Root Path is the common path present in the XML response. The Success Code is the successful HTTP response code expected by the respective Web Service operation. By default, the success code is 2**.

On the Response Mapping tab:

Below is an example of a schema that is mapped to XML response. Refer to Configuration for Response for more information.

On the XPAth Namespace Mapping tab:

The namespace xmlns is the default namespace for the example mentioned in this section, and it is represented as ns in the following screenshot.

On the General Information tab:

1. In the Operation Name field, enter Account Aggregation - 3 as the operation name.
2. From the Operation Type dropdown list, select Account Delta Aggregation.

3. In the Context URL field, enter the URL specific to the account delta aggregation. For example, the URL specified in the context URL is /users?filter=meta.lastModifiedDate gt "$application.lastAggregationDate_account$" ; where the lastAggregationDate_account is the last successful aggregation timestamp.

   Note

   The default time period is in format: "yyyy-MM-dd'T'kk:mm:ss'Z'" If you want to change the time period format, use the following key-value pair to update the source via API: key: connector_dateTimePatternvalue: "yyyy-MM-dd'T'kk:mm:ss'Z'" key : connector_serverTimeZonevalue: "UTC"

4. In the HTTP Method dropdown list, select GET.

On the Headers tab:

The Header has the data keys and their corresponding values. These key value pairs will be sent as part of the Header in the HTTP Request.

On the Response Information tab:

The Root Path is the common path present in the JSON response. The Success Code is the successful HTTP response code expected by the respective Web Service operation. By default, the success code is 2**.

On the Response Mapping tab:

Refer to Configuration for Response for more information about the raw JSON response on which the Response Information schema is mapped.

On the XPath Namespace Mapping tab:

The namespace xmlns is the default namespace for the example mentioned in this section, and it is represented as ns.

On the Parent Endpoint tab:

From the Parent Endpoint Name dropdown list, if needed select the endpoint on which the current operation is dependent to process the request.

On the Paging tab:

1. In the Initial Page Offset, select the page offset required.
2. From the Page Size, select the required page size for delta aggregation.
3. In the Paging Steps field, enter any necessary paging steps defined.

On the General Information tab:

1. In the Operation Name field, enter Get Object (XML) as the operation name.
2. From the Operation Type dropdown list, select Get Object.
3. In the Context URL field, enter the URL specific to the get object.
4. In the HTTP Method dropdown list, select POST.

On the Header and Body tab:

The Header has the data keys and their corresponding values. These key value pairs will be sent as part of the Header in the HTTP Request.

The HTTP body is used for posting the data with a request. The body has two data entry types, Form Data and Raw. The XML format does not support Form Data.

In the Raw field, enter the XML payload for the get object.

The $nativeIdentity$ signifies the AccountID (identity attribute) in the plan or during the get object operation. For example, nativeIdentity is used along with the following keywords:

• getobject - $getObject.nativeIdentity$
• plan - $plan.nativeIdentity$

On the Response Information tab:

The Root Path is the common path present in the XML response. The Success Code is the successful HTTP response code expected by the respective Web Service operation. By default, the success code is 2**.

On the Response Mapping tab:

Below is an example of a schema that is mapped to XML response. Refer to Configuration for Response for more information.

On the XPath Namespace Mapping tab:

The namespace xmlns is the default namespace for the example mentioned in this section, and it is represented as ns in the following screenshot.

On the General Information tab:

1. In the Operation Name field, enter Add Entitlement (XML) as the operation name.
2. From the Operation Type dropdown list, select Add Entitlement.
3. In the Context URL field, enter the URL specific to the entitlement.
4. In the HTTP Method dropdown list, select POST.

On the Header and Body tab:

The Header has the data keys and their corresponding values. These key value pairs will be sent as part of the Header in the HTTP Request.

The HTTP body is used for posting the data with a request. The body has two data entry types, Form Data and Raw. The XML format does not support Form Data.

In the Raw field, enter the XML payload for the entitlement.

On the Response Information tab:

The Root Path is the common path present in the XML response. The Success Code is the successful HTTP response code expected by the respective Web Service operation. By default, the success code is 2**.

On the General Information tab:

1. In the Operation Name field, enter Enable Account (XML) as the operation name.
2. From the Operation Type dropdown list, select Enable Account.
3. In the Context URL field, enter the URL specific to the account.
4. In the HTTP Method dropdown list, select POST.

On the Header and Body tab:

The Header has the data keys and their corresponding values. These key value pairs will be sent as part of the Header in the HTTP Request.

The HTTP body is used for posting the data with a request. The body has two data entry types, Form Data and Raw. The XML format does not support Form Data.

In the Raw field, enter the XML payload for the account.

Here the plan.nativeIdentity keyword signifies the AccountID (identity attribute) in the account request of the plan. For example, nativeIdentity is used along with the following keywords:

• getobject - $getObject.nativeIdentity$
• plan - $plan.nativeIdentity$

On the Response Information tab:

The Root Path is the common path present in the XML response. The Success Code is the successful HTTP response code expected by the respective Web Service operation. By default, the success code is 2**.

On the General Information tab:

1. In the Operation Name field, enter Disable Account (XML) as the operation name.
2. From the Operation Type dropdown list, select Disable Account.
3. In the Context URL field, enter the URL specific to the account.
4. In the HTTP Method dropdown list, select POST.

On the Header and Body tab:

The Header has the data keys and their corresponding values. These key value pairs will be sent as part of the Header in the HTTP Request.

The HTTP body is used for posting the data with a request. The body has two data entry types, Form Data and Raw. The XML format does not support Form Data.

In the Raw field, enter the XML payload for the account.

Here the plan.nativeIdentity keyword signifies the AccountID (identity attribute) in the account request of the plan. For example, nativeIdentity is used along with the following keywords:

• getobject - $getObject.nativeIdentity$
• plan - $plan.nativeIdentity$

On the Response Information tab:

The Root Path is the common path present in the XML response. The Success Code is the successful HTTP response code expected by the respective Web Service operation. By default, the success code is 2**.

On the General Information tab:

1. In the Operation Name field, enter Update Account (XML) as the operation name.
2. From the Operation Type dropdown list, select Update Account.
3. In the Context URL field, enter the URL specific to the account.
4. In the HTTP Method dropdown list, select POST.

On the Header and Body tab:

The Header has the data keys and their corresponding values. These key value pairs will be sent as part of the Header in the HTTP Request.

The HTTP body is used for posting the data with a request. The body has two data entry types, Form Data and Raw. The XML format does not support Form Data.

In the Raw field, enter the XML payload for the account.

On the Response Information tab:

The Root Path is the common path present in the XML response. The Success Code is the successful HTTP response code expected by the respective Web Service operation. By default, the success code is 2**.

On the General Information tab:

1. In the Operation Name field, enter Change Password (XML) as the operation name.
2. From the Operation Type dropdown list, select Change Password.
3. In the Context URL field, enter the URL specific to the password change.
4. In the HTTP Method dropdown list, select POST.

On the Header and Body tab:

The Header has the data keys and their corresponding values. These key value pairs will be sent as part of the Header in the HTTP Request.

The HTTP body is used for posting the data with a request. The body has two data entry types, Form Data and Raw. The XML format does not support Form Data.

In the Raw field, enter the XML payload for the account.

On the Response Information tab:

The Root Path is the common path present in the XML response. The Success Code is the successful HTTP response code expected by the respective Web Service operation. By default, the success code is 2**.