Intro

This API helps you in the process of providing the necessary data to your workfloo

🚧
Simplify your execution steps
Remember that you can skip the execution of this API in your workfloo if you choose to send the form data directly in the workfloo execution API call. Make sure the form is the next step in the flow after executing the workfloo. For more details, check the execute a workfloo API documentation.

Important points

To make the request it is only necessary to provide the workfloo ID generated in the workfloo platform.

Path parameter

You must send in the URL as a path parameter, the workfloo identifier that you generated in the initial step of executing a workfloo.

For example:

Sandbox

https://sandbox.workfloo.kiban.com/api/v1/workfloo/657118e1d511b6e54fe2a969/form

Production

https://workfloo.kiban.com/api/v1/workfloo/657118e1d511b6e54fe2a969/form

Request Body

To apply the query, the parameters defined in the form must be sent in the body.

If you want to know the required parameters, you can make a query without any parameters in the body by simply sending the empty JSON parentheses {} . The response will indicate the parameters that are required to execute the query.

Another way to know the parameters is to enter the edition of your form, for each of the fields there will be the following definition and each of them will have a configuration button.

Once you have entered each of the configuration buttons by clicking in the Edit section, you will be able to view the identifier of each field.

We cannot tell you exactly a request, because it will depend entirely on the fields you have defined in your form, but we can give you the following example of a JSON to consult a person to the Credit Bureau service.

{
    "first_name" : "FIRST",
    "second_name" : "SECOND",
    "last_name_1" : "KIBAN",
    "last_name_2": "CLOUD",
    "birth_date" : "1990-08-15",
    "rfc_pf" : "KIBA801010BPA",
    "address" : "AV PASEO DE LA REFORMA 403",
    "postal_code" : "06500"
}

Successful response

A successful response will only return a 200 http code, you will not get a body.

Listing the possible error responses

Format and required errors (Just as example)

When there is an error in the body sent, this may happen because a required parameter was not sent or the shared format is not appropriate. In any case, the error will be indicated so that it can be solved.

{
    "typeError": "REQUIRED_FIELDS",
    "errors": {
        "idWorkflooDefinition": "required"
    },
    "errorMessage": ""
}

Required scenarioId

You will get a 400 bad request error when the idWorkflooDefinition is not provided in the request body.

{
    "typeError": "ELEMENT_NOT_EXIST_ERROR",
    "errors": null,
    "errorMessage": "scenarioId not found"
}

Does not exits execution Id

The execution id provided does not exist, the service will return a 404 without a response body.

Unauthorized

It means that the provided API is incorrect and that you are not authorized to access it. You will not receive a body, only a 401 HTTP code.