Solved: Re: Business Data Transaction API - 404 Bad Reques...

expense_pcm

I set up Postman with my projects certificates, and I can get a successful response from the helloworld endpoint. However, when I post to the Business Data Transaction API, I get a 404 response.

I am posting to https://sandbox.api.visa.com/cdsapi/commercial/v1/ob/trxndata. I have updated Postman to use the correct certificates and credentials for my project.

The body of my request is

{
    "bank": [
        {
            "bankId": "999999"
        }
    ]
}

In response, I get the following HTML.

<!DOCTYPE html
	PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">

<head>
	<META HTTP-EQUIV="CONTENT-TYPE" CONTENT="TEXT/HTML; CHARSET=utf-8" />
	<title>Error</title>
</head>

<body>
	<H2>Error</H2>
	<table summary="Error" border="0" bgcolor="#FEEE7A" cellpadding="0" cellspacing="0" width="400">
		<tr>
			<td>
				<table summary="Error" border="0" cellpadding="3" cellspacing="1">
					<tr valign="top" bgcolor="#FBFFDF" align="left">
						<td><STRONG>Error</STRONG></td>
					</tr>
					<tr valign="top" bgcolor="#FFFFFF">
						<td>This page can't be displayed. Contact support for additional
							information.<br/>The incident ID is: N/A.</td>
					</tr>
				</table>
			</td>
		</tr>
	</table>
</body>

</html>

I would appreciate any help troubleshooting this. I was unable to find any sample code for the Business Data Transaction API. If that exists, I imagine it would make clear what I am doing wrong.

Regards,

Jason

SLi

Hi @expense_pcm,

If you are able to connect to the helloworld endpoint with your project certificates, that means your credentials and Postman setup are good.

Can you please share what payload you are sending to the Business Data Transaction API request? Please also share the response body showing the error message and the response header with the x-correlation ID. We'll be able to troubleshoot further with the additional information you provide us. 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.

expense_pcm

Thanks for your quick response. I just noticed that there are some invisible characters resulting from me copying and pasting the URL into postman. Now I get a slightly more useful reponse.

Postman is sending the following request headers:

Authorization: Basic R0o0T1dGRE5KQ0VGRVE3RDRVVEgyMUE0VFRucG45VWtaQkUxWkFIT1JaemVrMWxBNDpxRVg0WmVKbFIxQjRBOVU4ak9HY1c1OEF6QVhTVWg1enQ=

Content-Type: application/json

User-Agent: PostmanRuntime/7.26.10

Accept: */*

Cache-Control: no-cache

Postman-Token: 9e078a5f-85ea-43aa-945b-4588849883aa

Host: sandbox.api.visa.com

Accept-Encoding: gzip, deflate, br

Connection: keep-alive

Content-Length: 80

Along with the following request body:

{ "bank": [ { "bankId": "999999" } ] }

Then I get the following response headers

Server: nginx

Date: Wed, 14 Apr 2021 18:00:55 GMT

Content-Type: application/json

Content-Length: 208

Connection: keep-alive

X-SERVED-BY: l73c017

X-CORRELATION-ID: 1618423255_669_520009982_l73c017_VDP_WS

X-Backside-Transport: OK OK,OK OK

Cache-Control: no-cache, no-store, must-revalidate

Pragma: no-cache

Expires: -1

X-Download-Options: noopen

Strict-Transport-Security: max-age=31536000;includeSubDomains ,max-age=2592000;includeSubdomains

Strict-Transport-Security: max-age=15768000;includeSubdomains;always

X-Frame-Options: SAMEORIGIN

X-Content-Type-Options: nosniff

X-XSS-Protection: 1; mode=block

X-Global-Transaction-ID: 1adcbd1660772dd71d9ce139

X-APP-STATUS: 200

And the following response body:

{

"transactionData": {

"responseMetadata": {

"requestId": "1618423255_669_520009982_l73c017_VDP_WS"

},

"starterInfo": {},

"transactionRecords": "Improper request provided by user. Please check your request and retry."

}

I am simply using the request body example from the API Reference (https://developer.visa.com/capabilities/vbds/reference#vbds__transaction_data).

I just noticed that the reference says that a clientId request header is required. I am not aware if this ID. How do I obtain this value?

SLi

Hi @expense_pcm,

Thank you for sharing additional details on the error. This is very helpful and I was able to recreate the error on my end by sending the same payload you sent. I am working with the product team to get the correct payload. Please stay tuned.

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

Hi @expense_pcm,

Please try below payload and let me know how it goes. In case of error, please share the x-correlation id from the response header. Thanks.

{

"issuer": {

"metadata": {

"startDate": "2021/03/01",

"endDate": "2021/03/20",

"startIndex" : 0

},

"bank": [{

"regionId": 1,

"processorId": 1,

"bankId": "999999",

"company": [

{

"companyId": "12345"

}

]}]

}

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.

Re: Business Data Transaction API - 404 Bad Request

Business Data Transaction API - 404 Bad Request

Re: Business Data Transaction API - 404 Bad Request

Re: Business Data Transaction API - 404 Bad Request

Re: Business Data Transaction API - 404 Bad Request

Re: Business Data Transaction API - 404 Bad Request