Enable Account
This topic provides an example of an XML response for an enable account operation.

-
In the Operation Name field, enter Enable Account (XML) as the operation name.
-
From the Operation Type drop-down list, select Enable Account.
-
In the Authentication URL field, enter the URL specific to the account.
-
In the HTTP Method drop-down list, select POST.

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$
Note
If the target system expects the complete account object as payload, you must write a Before Operation Rule to fetch the complete object details and update the body attribute endpoint. Refer to Web Services Before Operation Rule for more information.

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**.