Longtext

POST /v1/form/update

Below is an example illustrating the consumable format of LongTextComponent. The 'NEXT' status indicates that you haven't reached the end of the form yet. Each question is uniquely identified by an ID stored in 'questionId'.

Object

{
    "status": "NEXT",
    "refId": "SLH-4UN0RDF0990D",
    "question": {
        "questionId": "0cf25539-7d62-4adf-9ffe-1754f090bda1",
        "question": "Why do you want this job?",
        "kind": "LongTextComponent",
        "settings": {}
    },
    "review": [
        ...,
        {
            "id": "c6730778-46ca-4fb2-ad73-ec5e9d2b1071",
            "question": "What is your full name?",
            "answer": "James Don"
        }
    ],
    "message": null,
    "invoice": {
        "title": "Question Engine All cards No logic",
        "quantity": 1,
        "currency": "XOF",
        "totalCost": 1000.0
    }
}

Response to the question

Headers

Name	Value
Content-Type	application/json
CLIENT_ID	<client id>

Body

In addition to the API keys specified in the Headers, ensure to include the eServiceId, refId, questionId. Upon a successful request, you will receive the next question. You'll recognize reaching the end of the form when the status is 'COMPLETED'.

values class field(s)	Format
value	string

Example

Request Body

{
    "eServiceId": "663835dfae67d8704b6752b7",
    "refId": "SLH-4UN0RDF0990D",
    "questionId": "0cf25539-7d62-4adf-9ffe-1754f090bda1",
    "values": {
        "value": "Because I am a genius."
    }
}

200

400