- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
I am currently testing Funds Transfer Attribute,Foreign Exchange Rate and Alias API.For all the named APIs,i am getting the following error
"
Solved! Go to Solution
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Enabling More Apis(Fx Api,Funds Attribute & Alias API)
Hey @JbJopito,
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.
Thanks,
Diana
Was your question answered? Don't forget to click on "Accept as Solution" to help other devs find the answer to the same question.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Enabling More Apis(Fx Api,Funds Attribute & Alias API)
1. End Point
https://sandbox.api.visa.com/visaaliasdirectory/v1/resolve
2. Request Header
Server | nginx |
X-Content-Type-Options | nosniff |
X-CORRELATION-ID | 1563298416_156_489914006_l73c017_VDP_WS |
Connection | close |
X-SERVED-BY | l73c017 |
Pragma | no-cache |
Date | Tue, 16 Jul 2019 17:33:36 GMT |
X-APP-STATUS | 403 |
X-Frame-Options | SAMEORIGIN |
Strict-Transport-Security | max-age=2592000;includeSubdomains |
Cache-Control | no-cache, no-store, must-revalidate |
Expires | -1 |
#status# | HTTP/1.1 403 Forbidden |
Content-Length | 122 |
X-XSS-Protection | 1; mode=block |
Content-Type | application/json;charset=UTF-8 |
3. Request Body{
"alias": "254711001987",
"businessApplicationId": "PP"
}
4. Response Header (include the x-correlation-id)
HTTP/1.1 403 Forbidden
Server: nginx
Content-Type: application/json;charset=UTF-8
Content-Length: 122
X-SERVED-BY: l73c017
X-CORRELATION-ID: 1563298416_156_489914006_l73c017_VDP_WS
X-APP-STATUS: 403
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Strict-Transport-Security: max-age=2592000;includeSubdomains
Cache-Control: no-cache, no-store, must-revalidate
Pragma: no-cache
Expires: -1
Date: Tue, 16 Jul 2019 17:33:36 GMT
Connection: close
5. Response Body
{"responseStatus":{"status":403,"code":"9611","severity":"ERROR","message":"Authorization Failed for the URL.","info":""}}
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hey @JbJopito,
The 403 (Forbidden) HTTP Status code indicates that this project does not have permission to access the requested resource. This can happen if you are trying to invoke API request for a resource that is not part of your project e.g. if you have created a project with Foreign Exchange Rates Product but are trying to use the same credentials to access Visa Consumer Transaction Controls.
403 (Forbidden) HTTP Status Resolution:
- Ensure that you are using a project and the credential for the project which includes the API being accessed
- Create a project and receive Sandbox credentials for the APIs being called
- Add the API being called (if not already included) to the project with credentials that are being used
Support > Frequently Asked Questions > I’m getting Error 403 – Forbidden. What does this mean and how can I resolve this? https://developer.visa.com/pages/support
403 Authorization Failed for the URL Resolution:
- It looks like this is a user/password authentication error. Please double check that you entered username and password correctly (e.g. make sure you are putting your email address as how you have entered it in the system, using lowercase or uppercase for characters that you had used lowercase or uppercase on and that there are no extra spaces)
- If you are getting a 403 error for two-way mutual SSL, the fix will be to generate credentials properly. Our Working with Visa APIs guide and Two-Way Mutual SSL authentication video will help you to resolve this issue. When you follow the instructions on this guide, please make sure to follow the instructions step by step and in its sequential order to resolve the issue. To access this guide and video please go here - https://developer.visa.com/pages/working-with-visa-apis/two-way-ssl
- This error usually means incorrect credentials. Can you please provide the API (url) you are invoking with the full request and response. Please mask any account or sensitive data like account numbers?
Thanks,
Diana
Was your question answered? Don't forget to click on "Accept as Solution" to help other devs find the answer to the same question.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Enabling More Apis(Fx Api,Funds Attribute & Alias API)
This is now sorted.Thank you
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Enabling More Apis(Fx Api,Funds Attribute & Alias API)
Hey @JbJopito,
Thanks for confirming the issue is now resolved! Have a good day!