Request API
The Send Request
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
You can get the base_url here.
Path Parameters
You can get the workspaceName here.
Header Parameters
The request body for an application with consent enabled is displayed below.
Request Body
app_id
stringRequired
It is a unique identifier that comes with every application created under ezto verify.
app_secret
stringRequired
Every application comes with an application secret upon being created, that can be rotated through the application.
request
json
This type consists of all the required data to be validated.
You can get the app_id and app_secret here.
{
"app_id": "2ed89c16-8cab-44c6-8329-0ac856276586",
"app_secret": "mU6yOWVP3QVzM0BFSkSL6P7gRNjeQUM40WTHrVufxHt1SByVUVJFynYNEZGzW1xT",
"request": {
"user": {
"metadata": {
"workflow":"onboarding"
}
},
"message": {
"consent": {
"type": "json",
"title": "Onboarding Request",
"message": {
"RequestFrom": "EventBeep",
"Purpose": "Onboarding"
}
}
}
}
}
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.) |