Hello Community,
I am using sample data for the sandbox when accessing the endpoint, "https://sandbox.api.visa.com/vti/v1/getioc". However, I am seeing a 500 response code when there is attempting send sample data. I see that I am able to authenticate successfully via the hello world endpoint. Below is that test using HTTPie (a curl alternative).
! http -a $VISAAPICLIENTID:$VISAAPIPASSWORD --cert-key=key.pem --cert=cert.pem https://sandbox.api.visa.com/vdp/helloworld -p=b
{
"message": "helloworld",
"timestamp": "2021-06-02T19:22:44"
}
Below is the test going to the getioc endpoint.
! http -a $VISAAPICLIENTID:$VISAAPIPASSWORD --cert-key=key.pem --cert=cert.pem "https://sandbox.api.visa.com/vti/v1/getioc" startDate==2017-05-19 endDate==2017-05-30 -p=bhH
GET /vti/v1/getioc?startDate=2017-05-19&endDate=2017-05-30 HTTP/1.1
Accept: */*
Accept-Encoding: gzip, deflate
Authorization: Basic REDACTED
Connection: keep-alive
Host: sandbox.api.visa.com
User-Agent: HTTPie/2.4.0
HTTP/1.1 500 Internal Server Error
Cache-Control: no-cache, no-store, must-revalidate
Connection: keep-alive
Content-Length: 94
Content-Type: application/json;charset=UTF-8
Date: Wed, 02 Jun 2021 19:24:51 GMT
Expires: -1
Pragma: no-cache
Server: nginx
Strict-Transport-Security: max-age=2592000;includeSubdomains
X-APP-STATUS: 500
X-CORRELATION-ID: 1622661890_850_973477050_l73c017_VDP_WS
X-Cnection: close
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
X-SERVED-BY: l73c017
X-XSS-Protection: 1; mode=block
{
"responseStatus": {
"info": "",
"message": "Internal server error",
"severity": "ERROR",
"status": 0
}
}
Any guidance on how I should modify my request to have a successful response is greatly appreciated. Thanks!
Solved! Go to Solution
Hi @bcunning91,
Apologies for the delay in responding. Our engineering team is still investigating this issue, I hope to have an update for you soon. If you are able to successfully call the helloworld endpoint, then your project credentials and connection to Visa is working properly. As soon as I hear back from our engineering team on the root cause of the Internal Server Error, I'll share it here. Thanks for your patience.
Thank you for investigating the issue. I am looking forward to hearing back on what you and the team find.
Cheers,
Brooks
Hi @bcunning91,
Thank you for your patience. Visa Payment Threat Intelligence is being decommissioned as a commercial product on Visa Developer and product team is in the midst of updating the documentation to reflect this. We apologized for the inconvenience caused, hope you will consider other APIs on Visa Developer. Please let us know if you have any questions.
@SLi Thank you for the update. Is there a recommended alternative to obtain similar information? I am very interested in exploring this particular use case from the existing documentation.
Firewall: IP addresses and domains from the IOC feed which are known to be malicious and unnecessary for daily operations can be blocked/quarantined/monitored at the firewall level to prevent connections and quickly detect malicious activity, helping to avoid breaches from occurring.
Source, https://developer.visa.com/capabilities/visa-payment-threat-intelligence/docs-how-to#section2
Hi @bcunning91,
We don't have another API on Visa Developer that provides all of the IOCs and reporting similar to what the Visa Threat Intelligence API offers, unfortunately. However, if you are a Visa client, you can access our Visa Online page. The security alerts and report on the Payment Systems Intelligence are available on Visa Online.