Testing VRM Transaction Feed via Postman

SOLVED
Highlighted
Regular Visitor

Testing VRM Transaction Feed via Postman

Hi,

 

I'm playing around with the VRM API, more specifically the transaction feed using Postman.

 

I am performing a POST on the following endpoint:

https://sandbox.api.visa.com/visariskmanager/v1/transaction/feed

 

I am specifying the service type as case creation and supplying the app user id that is provided in the test data.

 

I have also double checked that the certificate is still valid and that Postman is still making use of the certificates.

 
Yet I am receiving the following response.
 
{
    "responseStatus": {
        "code""9501",
        "severity""ERROR",
        "message""Requested Content Type is Not Allowed for API",
        "info""",
        "status""415"
    }
}

 

I'm not quite sure how to proceed from here

 
 
 
3 REPLIES 3
Highlighted
Visa Dev Moderator

Re: Testing VRM Transaction Feed via Postman

Hey @Mickey,

 

I'm happy to help. For Visa Developer Error Codes, please go here and scroll down to 415 - https://developer.visa.com/pages/visa-developer-error-codes

 

HTTP STATUS: UNSUPPORTED MEDIA TYPE

HTTP CODE: 415

CAUSE/RESOLUTION: The project is using an unsupported content type in the request.

 

If the issue persists, 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.

 



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

Thanks,
Diana

Highlighted
Regular Visitor

Re: Testing VRM Transaction Feed via Postman

Hi @DianaTran,

 

Thank you for your response, after reviewing your response and the contents of the the link you sent I started having a look at my configuration.

 

It seems that my body change from json to text, correcting this resolved the issue.

 

Another question, below is the sample request body for the transaction feed.

{
"serviceType": "Case Creation",
"alertStartTime": "20170530074012",
"alertEndTime": "20170530075012",
"appUserId": "marma2432f"
}

 

Under the request attribute it states that  alertStartTime and alertEndTime are optional, if I remove them from my request I get a response of 

{
    "id""1586334519_066_202662538_l73c018_VDP_WS",
    "hasMore""N",
    "code""E-100096",
    "message""Invalid Request. Case Creation Service Type request should contain alertStartTime and alertEndTime."
}
 
and if I include them with a date not older than 7 days and not more than 10 minutes apart between times, I then receive the following response. 
{
    "id""1586334656_160_1743090237_l73c015_VDP_WS",
    "hasMore""N",
    "code""E-100016",
    "message""Alert not found - No Content."
}
 
What I was hoping to achieve by not specifying a time frame was to receive all available created cases (which I suspect there aren't any on sandbox).
Highlighted
Visa Dev Moderator

Re: Testing VRM Transaction Feed via Postman

Hey @Mickey,

 

If you are getting that response, it’s not really an “error”. It means that for the query criteria (in this case, the time range in GMT for when alerts were created) that the client sent in the API, there were no alerts that exists that meet that criteria. In other words, in this case, the client is asking: “were there alerts created between the alert start time and the alert end time that can be downloaded?” Visa’s response is: “No, there are not alerts that were created between the start and end time.

 

 



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

Thanks,
Diana