This endpoint is mandatory to start any onboarding session in Incode Omni and session can be monitored on the Incode Dashboard. And it generates token which should be used for the authentication of future subsequent calls.
API reference, Interview
Start onboarding
POST
https://demo-api.incodesmile.com/omni/startHeaders
Request body
application/json
Language code to be used when doing speech to text. Possible values: en-US, es-ES, pt-BR.
Id that identifies user in clients system should be used for externalId. (Deprecated, use externalCustomerId instead)
Id that identifies user in clients external system.
uuid key used in redis, can be used as an alternative to sending interviewId.
Id of the flow to be used for this onboarding.
Url the user will be redirected to after finishing the onboarding successfully.
Optional integration reference.
Url uuid key used in redis. Will be validated in start if qrPhishingResistance is ON.
Used to send any additional information in key value pair format. Max fields: {maxEntries}, max key length: {keyMaxLength}, max value length: {valueMaxLength}
Responses
Response body (application/json)
Identifies the onboarding session that is initialized. Can be used for fetching data about that session in future calls.
Internal JWT token used for the future subsequent calls. It is the value for X-Incode-Hardware-Id header in all other calls.
This value is used for connecting to conference call.
(only if configurationId is sent in request). Type of the flow used. Could be flow (in most cases), or legacy type configuration (not used anymore).
enum
configurationflowworkflowNumber of seconds after which manual capture button should be shown to the user, while capturing ID when ID is detected.
Number of seconds after which manual capture button should be shown to the user, if ID is not detected.
Number of seconds after which manual capture button should be shown to the user, while capturing selfie.
Number of ID captures after which user should be taken to next screen.
Number of selfie captures after which user should be taken to next screen.
Number of curp validations after which user should be taken to next screen. (only for Mexico)
Customer specific clientId that corresponds to api key.
Server environment. Could be one of: stage, demo, saas.
It's true if interviewId corresponds to an existing Onboarding Session.
Response body (application/json)
UTC timestamp in milliseconds
Custom error code or HTTP status code
HTTP status error
Custom error message
Endpoint path
Custom error details