Ezkra (KRA Microservice) Repush API

introduction this document details the api endpoint for the ezkra repush process, aimed at re submitting onboarding information for investors this functionality is critical for addressing instances where initial submissions fail or require re submission the api is a component of the ezkra preproduction platform, managed by signzy endpoint description url production https //backops investor onboarding preproduction signzy tech/kra handler/api/onboardings/repush https //backops investor onboarding preproduction signzy tech/kra handler/api/onboardings/repush pre prod https //backops investor onboarding preproduction signzy tech/ kra handler/api/onboardings/repush https //backops investor onboarding preproduction signzy tech/kra handler/api/onboardings/repush method post this endpoint is designed to re push the onboarding data for a specific investor identified by their onboarding id headers content type application/json application/json indicates json formatted request body accept application/json application/json specifies the response format expected to be json authorization bearer \<token> bearer \<token> authenticates the request replace \<token> \<token> with your actual bearer token request body the request body must be a json object containing the following key value pair onboardingid a string representing the unique identifier of the investor's onboarding session this id is critical for identifying the specific onboarding data to be re pushed sample request body { "onboardingid" "65xxxxxx9b" } curl example below is a curl command example to use this api, including all required headers and the sample request body curl location 'https //backops investor onboarding preproduction signzy tech/kra handler/api/onboardings/repush' \\ \ header 'content type application/json' \\ \ header 'accept application/json' \\ \ header 'authorization bearer \<your access token>' \\ \ data '{ "onboardingid" "65xxxxxx9b" }' note replace \<your access token> \<your access token> with your actual bearer token response the api response will contain details about the success or failure of the re push operation in case of success, it might return the updated status of the onboarding process or a confirmation message for failures, an error message detailing the reason will be provided sample response success { "onboardingid" "65xxxxxx19", "customerid" "65xxxxxxbd", "callbackurl" "", "message" "the application is in progress, and it has been repushed to kra" } error { "error" { "statuscode" 500, "name" "error", "message" "argument passed in must be a single string of 12 bytes or a string of 24 hex characters" } } error handling ensure the onboardingid onboardingid is correctly formatted and that the bearer token is valid and not expired handle http status codes properly, especially client side (4xx) and server side (5xx) errors security use https to secure data during transmission authentication via bearer token is required and must be safeguarded against unauthorized access conclusion the ezkra repush api is essential for maintaining the reliability of the investor onboarding process, allowing for the necessary re submission of onboarding data proper implementation and diligent error handling are crucial for a smooth onboarding experience getting help please feel free to contact us if you have any questions, require clarification, or have ideas for how to make the documents or any of our services better you can reach out to us at help\@signzy com