Trigger Request

The Transaction API provided by ezto verify is designed for initiating API calls that primarily purposes to trigger predefined transaction flows configured within the system.

Base URL

Path Params

Header Params

note

The request body for an application with consent enabled is displayed below.

Below is the request body structure for the Trigger request Enpoint

requestjson

Sample Request Body
{
  "user": {
    "metadata": {
      "workflow":"onboarding"
    }
  },
  "message": {
    "consent": {
      "type": "json",
      "title": "Onboarding Request",
      "message": {
        "RequestFrom": "EventBeep",
        "Purpose": "Onboarding"
      }
    }
  }
}

note

The request and response are different based on the application's configuration, which can be build using API Builder.

HTTP STATUS CODE SUMMARY
200	OK	Everything worked as expected.
400	Bad Request	The request was unacceptable, often due to missing a required parameter.
401	Unauthorized	No valid App secret or App ID provided.
402	Request Failed	The parameters were valid but the request failed.
403	Forbidden	The Application doesn't have permissions to perform the request.
404	Not Found	The requested resource doesn't exist.
500	Server Errors	Something went wrong on ezto verify's end. (These are rare.)