UserMangement ->Delete User
SandBox Request Url:
---------------------------
https://sandbox.api.visa.com/merchant-api-ic/client/users?apikey={apikey}
Query Parameters:-
1) apiKey Required string
2) username Required string
where i need to send username in Request URL ,if i send username like :
https://sandbox.api.visa.com/merchant-api-ic/client/users?username={username}&apikey={apikey}
getting below response
{
"responseStatus": {
"code": 2101,
"message": "Resource not found",
"severity": "ERROR",
"details": "",
"status": "NOT_FOUND",
"additionAttributes": { },
"info": "http://api.visa.com/docs/errors/2101"
}
}
if i send Request like :https://sandbox.api.visa.com/merchant-api-ic/client/users?apikey={apikey}
getting below response
Respose:-
{server: "Apache", x-served-by: "l73c022", x-correlation-id: "1527066045_968_87_l73c022_VDP_ARM",…}
response:
{
"responseStatus": {
"code": 2098,
"message": "Invalid Request",
"severity": "ERROR",
"details": "Required String parameter 'username' is not present",
"status": "BAD_REQUEST",
"additionAttributes": { },
"info": "http://api.visa.com/docs/errors/2098"
}
}
Hi @Msvarma,
Can you please provide more information on the error you've received? Please send the response request of the error received, screenshots and the Correlation ID.
Below are the steps to get the Correlation ID using a Google Chrome browser.
1>Open Chrome menu.
2>Click on More tools then Developer tools.
3>Check the box to Preserve Log for the Network Tab.
4>Then try to click on the add API link.
5>You can find the Correlation ID in the network log for add API call.
Hai Please resolve the mentioned issue.
Hi @Msvarma,
Thank you for your inquiry. Can you please make sure you are using the right credentials, such as username and password?
In addition to that, the issue could also be caused by the Certificates not being sent with the request. Check File->Settings->SSL Settings and make sure the KeyStore and KeyStore Password are populated in Soap UI.
The Certificate Signing Request is a prerequisite to get your application certificate (cert.pem), which is required to establish a two-way SSL connection. Additionally, you will need a root certificate (VICA-SBX.pem) and your private key.
You have two options to generate a Certificate Signing Request (CSR):
Have Visa generate a CSR for you (recommended)
Select "generate a CSR from me" when you create a new Visa Developer application. When you select this option, Visa will generate a CSR for you, and you will be prompted to save your private key file when it is downloaded through your browser. Once you save your private key, go to your Visa app page and download your client certificate (cert.pem), as well as your root certificate (VICA-SBX.pem). You will then have everything you need to create a key store.
Generate your own CSR
You can choose to create your own CSR. The Visa Developer Getting Started Guide provides detailed steps on how to generate CSRs: https://developer.visa.com/vdpguide#twowayssl. Please note that you have to fill out all required fields in your Certificate Request. Also, note that the organization name and unit fields do not accept punctuation characters – your CSR will be deemed invalid if you use these characters. Once you have a CSR file, go ahead and create a Visa app, choose "Submit my own CSR", and upload your CSR file. During the CSR creation process, take note of the file containing your private key. Once you upload your CSR, go to your Visa app page, and download your client certificate (cert.pem), as well as your root certificate (VICA-SBX.pem). You will then have everything you need to create a key store.
Continuing to the Key Store
Once you have a private key and two certificate files in your local directory, you will need to combine them into a key store. You can decide whether to use Java Key Store (JKS) or PKCS (P12) key store, depending on what your development environment requires. There are sections in “getting started” ->“Using two-way SSL” (https://developer.visa.com/vdpguide#twowayssl), that describe how to create each type of key store, please follow those steps. Note, that the root certificate is not needed for a P12 file, you can create a P12 file out of two files: private key and cert.pem
If you are still getting an error please provide more information on the error you have received. Please send the response request of the error received, screenshot and the Correlation ID.
Below are the steps to get the Correlation ID using a Google Chrome browser.
1>Open Chrome menu.
2>Click on More tools then Developer tools.
3>Check the box to Preserve Log for the Network Tab.
4>Then try to click on the add API link.
5>You can find the Correlation ID in the network log for add API call.
Please perform these steps and let me know your findings.