Callback URL Integration
A guide to specify the requirements to implement a callback URL which will be invoked by the eNROLL after client enrollment to sync his/her enrollment data with the target organization.
Last updated
A guide to specify the requirements to implement a callback URL which will be invoked by the eNROLL after client enrollment to sync his/her enrollment data with the target organization.
Last updated
Success callback: will be invoked by the eNROLL to sync Approved enrollments.
Fail callback: will be invoked by the eNROLL to sync Rejected enrollments.
Success CallBack url: the url of the callback api will be invoked by the eNROLL to sync Approved enrollments.
Faild CallBack url: the url of the callback api will be invoked by the eNROLL to sync Rejected enrollments.
Token url: will be invoked by the eNROLL to obtain an access token.
Client Id: string will be send in the header of request for authentication
Client Secret: string will be send in the header of request for authentication
There are two separate callback URLs and an authorization token endpoint that must be implemented by the organization wishing to integrate with eNROLL:
a. Authorization Token Endpoints
POST
{{Your Token url}}
Content-Type
Set to application/x-www-form-urlencoded
client_id
String
Provided by the organization.
Must be registered in callback URLs screen in the eKYC Org Admin Panel.
client_secret
String
Provided by the organization.
Must be registered in callback URLs screen in the eKYC Org Admin Panel.
grant_type
String
Set to client_credentials
{
"access_token": "string",
"expires_in": βintβ,
"token_type": "Bearer",
}
POST
{{Your Provided Callback URL}}
Callback-Test
String
This header will be sent only when a Test attempt is performed to verify that the callback URL is up.
The org should ignore the request payload when this header is present.
applicants
List of applicants
If Callback-Test header is present, then return 200 Ok
isUpdate
true if the callback for update request
applicantId
unique identifier for each application
gender
ex: "M" or "F"
phoneNumbers
ex:["+201068282888","+201068282882"]
emails
ex:["a@b.c","x@y.z"]
livePhotoPath
Live Photo Path Captured in Face Matching Step
firstName
first line of name in national id
familyName
second line of name in national id
address
first line of address in national id
state
second line in address in national id
idNumber
ex: "29703012357788"
documentNumber
Factory Naumber
documentTypeCode
ex: "EGY"
issueDate
issue date for document
nationality
ex: "EGY"
idFrontScanPath
file name to be get using images api
idBackScanPath
file name to be get using images api
photo
fetched from id document. file name to be get using new api
passportScanPath
file name to be get using images api
issuingAuthority
ex: "EGY"
status
ex :
Accepted = 1,
ManuallyAccepted = 4,
ManuallyRejected = 5
There are also an optional end points that organization could use to get specific applications during a period of time
Token generation:
this is an Api to generate token using tenantId, tenantSecret.
Get Applicant Id By Request Id :
Get applicants By Request ID OR Correlation Id:
Get applicants during specific date
Get applicants by list of applicantId:
Get image as base64 by ImagePath:
Get list of images by list of ImagePaths:
Success
Success
Success
Success
Success