Process Journey Step

Overview

The Process Journey Step API is designed to support the asynchronous handling of various stages in a user's journey. It is capable of processing different types of steps, such as ID document step, selfie step, and other custom steps that may be required for specific needs.

Usage Guidelines

  1. Start the Onboarding Journey: To use this API you must initiate a new user onboarding journey by sending a request to the API to process a journey step.
  2. Make an API Call: Submit the necessary image data and parameters for the journey step through this API. If there are multiple steps involved, repeat this process for each step.
  3. Monitor Processing Status: Since this API operates asynchronously, check the status of the processing step by using the Get Journey Summary API.

Supported Image Image

Here you can find more info about the supported image size and dimension

Request Content Types

This API supports two content types for submitting data:

  1. multipart/form-data (Preferred)
    Binary files are sent as multipart form fields alongside other textual/string fields. This is the recommended approach as it is more bandwidth-efficient.
  2. application/json
    All fields are submitted as a JSON payload. Binary files (image, image2) must be base64-encoded strings. Make sure to set the Content-Type header to application/json.
🚧

Base64 encoding binary data increases the payload size by approximately 33%. For large image files, this can significantly impact performance and bandwidth. Use multipart/form-data whenever possible.

Base URL by Region

The base URL you should use depends on the region where your services are hosted. Below are the available URLs for each region. By default, the EU region URL is used.

Authentication

For information on API credentials and the authentication process, please visit the API Credentials and Authentication page for comprehensive details.

Body Params
string
required

The id of the current journey.

string
required

The step id of the current step in the process. Like 0 or additional_face

file
required

The image file for processing the current step.

file

The second image file for processing the other document side.

string

A boolean value indicates that the user wants to skip this step.

additional_data
object

Additional data that can be sent with the request. This is optional and can be used to send any extra information required for the step.

Responses

Language
Credentials
Basic
base64
:
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json