<request type="IMPORT_PARTICIPANTS" desc="Importing Participants">
<parameters>
<parameter name="APPLICATION" value="SAMPLE1"/> (1)
</parameters>
<contents>
ADD_OR_UPDATE_PARTICIPANT, HDR, LABEL, NAME:ja, .... (2)
ADD_OR_UPDATE_PARTICIPANT, DTL, "S01","Roppongi Store",....
ADD_OR_UPDATE_PARTICIPANT, DTL, "S02","Daikanyama Store",....
....
</contents>
</request>Importing Participants
This manual is in pilot operation.
|
Overview
This function is the same as "Importing Participants" performed via fusion_place [Manager]. In other words, it allows bulk addition, updating, or deletion of participants.
How to Write a Request
Below is an example request for "Importing Participants":
| 1 | "Application" parameter |
| 2 | Request content |
Parameters
Specify the target application for the import.
| Parameter | Required | Key | Description |
|---|---|---|---|
APPLICATION |
Yes |
None |
Specify the label of the target application. |
Request Content
The request content consists of the data to be imported. The format is the same as when importing participants via fusion_place [Manager] (however, replacing special characters <, >, & is required). For more details, refer to:
Response Content
Below is an example response for "Importing Participants":
<response type="IMPORT_PARTICIPANTS" desc="Importing Participants">
<returned-contents> (1)
</returned-contents>
<result>
<code>ERROR</code> (2)
<started-at time-zone="Asia/Tokyo">2015/07/28 09:50:04.227</started-at>
<ended-at time-zone="Asia/Tokyo">2015/07/28 09:50:07.828</ended-at>
<messages>
Access permission type field "ACCESS_PERMISSION_TYPE" specified... (3)
...
</messages>
</result>
</response>| 1 | Returned Content |
| 2 | Processing Result Code |
| 3 | Message |
