Introduction
...
HEADER PARAMETERS:
Content-Type (*required) |
Media types can be:-
|
X-Channel-ID (*required) |
It the Unique Id to identify the root organization to which the user belongs |
REQUEST BODY: multipart/form-data
file (*required) |
This is a .csv file. Each line of the file is a data record, separated by commas |
...
REQUEST BODY: application/JSON:
fileUrl (*required) |
|
Additional Properties (Optional) | createdBy, questionType, author, stage OR status |
...
Code Block | ||
---|---|---|
| ||
{ "id": "api.v1.bulkupload", "ver": "1.0", "ts": "2021-10-20T09:20:59.943Z", "params": { "resmsgid": "09faf370-3187-11ec-b57e-5ffde477525a", "msgid": "095a6db0-3187-11ec-b57e-5ffde477525a", "status": "successful", "err": null, "errmsg": null }, "responseCode": "OK", "result": { "processId": "112ed159-c805-4df5-9da3-3fcd73122cc2", } } |
Scenario | API |
---|---|
Bulk upload Questions only |
|
Bulk upload Questions and link them to QuestionSet |
|
Bulk upload Questions and link them to section under QuestionSet |
|
Bulk upload Questions with common metadata |
|
Solution 2:
Create a generate QuML API for various interaction types such that it takes required parameters as input and generates a QuML output. The API takes input as an array of questions.
...
HEADER PARAMETERS:
Content-Type (*required) |
The possible media types can be:-
|
X-Channel-ID (*required) |
It the Unique Id to identify the root organization to which the user belongs |
...