Backend error for VMSS API call via Postman

MKolda
New Contributor

Backend error for VMSS API call via Postman

Hi, 

I am trying to test the VMSS API via Postman but every API call returns API003 - 

Backend Error - Orchestration couldn't complete. I have set up the two ssl connection (connection for Helloworld is working). Am I doing something wrong? Is the MLE for the VMSS sandbox also required?
6 REPLIES 6
DianaTran-Yee
Visa Developer Support Specialist

Re: Backend error for VMSS API call via Postman

Hey @MKolda,

 

I'm happy to help resolve the issue. To continue, please provide the following information:

1. Endpoint
2. Request Header
3. Request Body
4. Response Header (include the x-correlation-id)
5. Response Body

Using SoapUI, you can find the x-correlation-id in the Raw Tab of the response header.

 

Please navigate to our Visa Developer Error Codes page to learn how to resolve error codes here  - https://developer.visa.com/pages/visa-developer-error-codes 

 

If you don't find an error code listed here, refer to the API-specific error codes in its respective documentation pages. 




Thanks,

Diana



Was your question answered? Don't forget to click on "Accept as Solution" to help other devs find the answer to the same question.

MKolda
New Contributor

Re: Backend error for VMSS API call via Postman

Hi,

1. Endpoint: https://sandbox.api.visa.com/vmss/service/v1/searchTerminatedRequest

2. Headers:

Accept: application/json
keyId: f24baxx8-9261-4xxe-8e5x-a01xx06c8exx
Authorization: Basic xxxxxxx
Content-Type: application/json
3. Body is a sample used for the APi doc:

 

{
"searchTerminatedRequest": {
"terminatedRecordSearchCriteria": {
"legalName""Snap Photoshop Ltd",
"webAddresses": [
],
"businessEmailAddress""billsmith@snapphoto.com",
"address": {
"countryOrRegion""AT",
"stateOrProvince""CA",
"city""St Albans",
"streetAddress""80 Wood Street",
"zipOrPostalCode""SA82GF"
},
"taxID""999999",
"businessRegistrationNumber""999999",
"tradeOverInternet"false,
"merchantCategoryCodes": [
"5411",
"7211",
"742"
],
"principals": [
{
"name""Bill Smith",
"SSN""123-12-1234",
"businessPhoneNumber""+861071111222"
}
],
"category""0",
"businessPhoneNumbers": [
"+861071111222",
"+861071111221"
],
"DBAName""Snap Photoshop Ltd"
},
"acquirerBID""99999999",
"retroAlertIfNoMatch"false,
"globalSearch"true,
"acquirerCountryOrRegion""JP"
}
}
 
4. Content-Type: application/json
X-SERVED-BY: l73c013
X-CORRELATION-ID: 1611836006_194_387470150_l73c013_VDP_WS
response-message-id: 2ab56386-1022-4975-aabb-3be86bea2d5a
X-AGS-Request-ID: v3:8651:sandbox:73c010:70c3dfde326891f53b1765912557dcab
X-APP-STATUS : 500
 
5. 
{
    "responseStatus": {
        "statusCode""API003",
        "statusDescription""Backend Error - Orchestration couldn't complete"
    }
}
 
SLi
Visa Developer Support Specialist
Visa Developer Support Specialist

Re: Backend error for VMSS API call via Postman

Hi @MKolda ,

 

This API requires MLE, have you try encrypting the payload first before sending the request? Thanks.


Best,
Stacey

Was your question answered? Don't forget to click on "Accept as Solution" to help other devs find the answer to the same question.
MKolda
New Contributor

Re: Backend error for VMSS API call via Postman

I see in my project dashboard that it's N/A:

 

 
 

2021-02-01_08h27_38.png

SLi
Visa Developer Support Specialist
Visa Developer Support Specialist

Re: Backend error for VMSS API call via Postman

Hi @MKolda,

 

The error might not be related to MLE. I have asked our tech team to investigate and will get back with an update as soon as I have something to share. Thanks for your patience.


Best,
Stacey

Was your question answered? Don't forget to click on "Accept as Solution" to help other devs find the answer to the same question.
SLi
Visa Developer Support Specialist
Visa Developer Support Specialist

Re: Backend error for VMSS API call via Postman

Hi @MKolda,

 

Thank you for your patience. Our tech team confirmed that MLE is required for VMSS API. Please retry and encrypt the payload with your MLE key. The UI issue is being fixed and will be pushed out in the next release. Thanks again.


Best,
Stacey

Was your question answered? Don't forget to click on "Accept as Solution" to help other devs find the answer to the same question.