Merchant Search - Internal Application Error

[ethoca_PM2018]

From https://developer.visa.com/capabilities/merchant_search/reference, clicking "Send Request" from the default state returns:

"merchantSearchServiceResponse": {

• "header": {
  • "numRecordsMatched": 0,
  • "numRecordsReturned": 0,
  • "requestMessageId": "Request_001",
  • "messageDateTime": "2018-01-29T15:09:17.721",
  • "responseMessageId": "64VDP502020180129150917721",
  • "startIndex": "0",
  • "endIndex": "0"
  },
• "status": {
  • "statusDescription": "Internal Application Error",
  • "statusCode": "CDI120"
  }

}

[DianaVisaPM]

Hello,

Thank you for your inquiry. Can you please let me know if it is currently working again? If it's not, can you please send additional error information for investigation to developer@visa.com?

Please send the response request of the error received, screenshot and the Correlation ID.
 
To get the Correlation ID using a Google Chrome browser, please see steps below.
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.

If still receiving error, send this information to developers@visa.com.

Thank you,

Diana

[fredzilla]

I'm seeing the same failure.
Here's the response:

{
  "statusCode": 200,
  "body": {
    "merchantSearchServiceResponse": {
      "header": {
        "startIndex": "0",
        "numRecordsMatched": 0,
        "numRecordsReturned": 0,
        "requestMessageId": "1966d0df-c377-47ec-b8ef-6bc02586d971",
        "messageDateTime": "2019-06-12T18:03:13.241",
        "responseMessageId": "64VDP1743220190612180313241",
        "endIndex": "0"
      },
      "status": {
        "statusDescription": "Internal Application Error",
        "statusCode": "CDI120"
      }
    }
  },
  "headers": {
    "server": "nginx",
    "content-type": "application/json;charset=UTF-8",
    "content-length": "357",
    "x-served-by": "l55c016",
    "x-correlation-id": "1560362592_921_667684501_l55c016_VDP_WS",
    "x-backside-transport": "OK OK,OK OK",
    "cache-control": "no-cache, no-store, must-revalidate,no-cache, no-store, max-age=0 ,no-cache, no-store, must-revalidate",
    "pragma": "no-cache,no-cache ,no-cache",
    "x-download-options": "noopen",
    "expires": "-1,Thu, 01 Jan 1970 00:00:00 GMT ,-1",
    "content-language": "en-US",
    "x-global-transaction-id": "1607770237",
    "x-app-status": "200",
    "x-frame-options": "SAMEORIGIN",
    "x-xss-protection": "1; mode=block",
    "x-content-type-options": "nosniff",
    "strict-transport-security": "max-age=2592000;includeSubdomains",
    "date": "Wed, 12 Jun 2019 18:03:14 GMT",
    "connection": "close"
  },
  "request": {
    "uri": {
      "protocol": "https:",
      "slashes": true,
      "auth": null,
      "host": "sandbox.api.visa.com",
      "port": 443,
      "hostname": "sandbox.api.visa.com",
      "hash": null,
      "search": null,
      "query": null,
      "pathname": "/merchantsearch/v1/search",
      "path": "/merchantsearch/v1/search",
      "href": "<a href="https://sandbox.api.visa.com/merchantsearch/v1/search" target="_blank">https://sandbox.api.visa.com/merchantsearch/v1/search</a>"
    },
    "method": "POST",
    "headers": {
      "User-Agent": "VDP_SampleCode_Nodejs",
      "Authorization": "Basic VTQySTBYWFhVT1dUT0dLN1Q1UjMyMXR5bjFKd29Malg2Z1JoWUEwMUMwTHpFM0VCMDpjQTBCbjc4ZXJBMU8wR3duNg==",
      "x-correlation-id": "1OR1klywBTLv_SC",
      "x-client-transaction-id": "4858ddde-9805-47df-bf93-255e7b9ed506",
      "accept": "application/json",
      "content-type": "application/json",
      "content-length": 457
    }
  }
}

Not sure why it returns a 200 for a failure as well. That's not helpful.

[DianaVisaPM]

Hi @fredzilla,

To further investigate, please provide the following information:

1. End Point
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.

[DianaVisaPM]

Hey there @ethoca_PM2018 and @fredzilla,  

Are you still experiencing an issue? Please submit back to us the requested information so that we can provide you with further assistance. 

[fredzilla]

We've found another way to get this data.
Thank you for your time.

[DianaVisaPM]

Hey @fredzilla,

Thanks for letting us know that you have another way to get this data. So, I'm interested in learning more on what other way did you use to get the data that you were looking for.

Can you please share with the developer community what you did to get this data?

Thanks!

[fredzilla]

We're writing our own ML classifier.

[DianaVisaPM]

Hey @fredzilla,

That's awesome to hear! Thanks for letting us know. Please do not hesitate to submit another community forum post at any time if you need further assistance or have other questions.

Someone from the developer support team will be happy to help!