merchant search return only one record

[Guy]

I run the following api https://api.visa.com/merchantsearch/v1/search

With the following body:

{ "searchAttrList": { "merchantName":"Home Depot","merchantPhoneNumber":"","merchantUrl":"","merchantCountryCode": "840"}, "responseAttrList": [ "BBB" ], "searchOptions": { "wildCard": [ "merchantName" ], "maxRecord": "10","matchIndicators": "true", "matchScore": "true" }, "header": { "requestMessageId": "Request_001", "startIndex": "0" , "messageDateTime": "2019-08-07T14:25:21.000" } }

I get  the following response:

{

"merchantSearchServiceResponse": {

"response": [

{

"responseValues": {

"visaStoreName": "HOME DEPOT",

"visaMerchantName": "HOME DEPOT",

"businessLegalName": [],

"merchantCategoryCodeDesc": [

"HOME SUPPLY WAREHOUSE STORES"

],

"merchantCountryCode": "840",

"merchantCity": "CARSON CITY",

"merchantState": "NV",

"merchantPostalCode": "89701",

"merchantStreetAddress": "",

"paymentAcceptanceMethod": [

"F2F"

],

"terminalType": [

"SWIPE"

],

"firstTranDateRange": "",

"lastTranDateRange": "",

"merchantCategoryCode": [

"5200"

],

"visaMerchantId": "19961613",

"visaStoreId": "273697896",

"merchantUrl": [],

"merchantPhoneNumber": []

},

"matchIndicators": {

"merchantCountryCode": "Y",

"merchantName": "Y"

},

"matchScore": "14.641986"

}

],

"header": {

"startIndex": "0",

"numRecordsMatched": 3535,

"numRecordsReturned": 1,

"requestMessageId": "Request_001",

"messageDateTime": "2019-08-11T11:21:50.814",

"responseMessageId": "64VDP7687020190811112150814",

"endIndex": "0"

},

"status": {

"statusDescription": "Max Record Limit is:1, Please use start index to see the next set of records",

"statusCode": "CDI000MAXRCW"

}

}

}

Question:

Why the Api does not return 3 result as I requested (but only one)?

I set maxRecord=3 and numRecordsMatched=3535.

Thank you.

[API_Products]

Hey @Guy,

Are you using the Test Data provided to you in your project app?

If you're still experiencing an issue, 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.

[Guy]

Hi @DianaTran-Yee,

Thanks for your prompt reply.

This is a request we sent to Visa live environment.

Please see all details in the original question (end point, request and response).

We are not using the soap UI.

Any idea why we get only one record when we specify that we want more, and the response indicate that there are many more potential results.

Thank you,

Guy.

[API_Products]

Hey @Guy,

Can you please provide the x-correlation-id? The x-correlation-id is needed to help troubleshoot the issue and we can take a look at the logs using the x-correlation-id.

Instructions to get the x-correlation-id are provided below and if you need a guide to help you get SoapUI setup please go here - https://developer.visa.com/pages/working-with-visa-apis

Then click on the Authentication box from the Working with Visa APIs page select Two-Way SSL because that's the Authentication for Merchant Search API.

[poojaroyy]

hi .. i am new abie here 

[API_Products]

Hey @poojaroyy,

Is there anything I can do to provide you with assistance?                              

[ferrnado1]

I am getting the same error. I tried the solution provided in this thread but no luck

ferrnado

beetv apk

[API_Products]

Hey @ferrnado1,

To further investigate the problem you're experiencing, 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.