cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
5868
Views
5
Helpful
1
Replies

Return Code 403 - Forbidden (Access Denied) on several API's

CiscoAPI
Community Member

Hello, 

 

I've got some experience in using API's but I'm new to the Cisco API's. 

According to Cisco my account has the correct permissions using CCW-R (we're PSS) and Service API's. We registered the API's we want to use to two apps due to different auth methods - one for the CCW-R and one for Service API's. 

 

While some API's are working fine (e.g. EoX and Advisories) I've goth 'Access Denied' on other API's. For example: 

GET https://api.cisco.com/sn2info/v2/coverage/status/serial_numbers/FCW2323G0TV
GET https://api.cisco.com/product/v1/information/product_ids/UBR10012,ASR1001
GET https://apx.cisco.com/cs/api/v1/customer-info/customer-details
GET https://apx.cisco.com/cs/api/v1/customer-info/customer-details
POST https://api-test.cisco.com/ccw/renewals/api/v1.0/search/contractSummary

 

Can someone please give me a hint if I'm doing it wrong? 

 

Here are the API's registered for the service (please ignore, that the CCW-R is added as well):

01.png

The token request is working fine (using it for EoX and Advisories as well because it's the same app):

02.png

My request header is looking like the following:

03.png

According to the API and their documentation I add JSON information to the body. For example the customerID when trying to receive respective information. 

04.png

 

The response is always the same: 

05.png

 

I really appreciate your help! Thanks, David.

1 Accepted Solution

Accepted Solutions

CiscoAPI
Community Member

Ok, yesterday I had a call with Cisco and the problem ist solved. 

1) My permissions were insufficient and 

2) I did not know, that api* und apx* URL's are behind different gateways and need different authentication / client credentials due to different applications in use. 

api* URL is behind Mashery GW and uses the application(s) on https://apiconsole.cisco.com while

apx* URL is behind Mulesoft GW and uses the application(s) on https://anypoint.mulesoft.com/apiplatform/apx/#/portals

With having both in place and the correct permissions granted API access is working for CCW-R and Service APIs. 

View solution in original post

1 Reply 1

CiscoAPI
Community Member

Ok, yesterday I had a call with Cisco and the problem ist solved. 

1) My permissions were insufficient and 

2) I did not know, that api* und apx* URL's are behind different gateways and need different authentication / client credentials due to different applications in use. 

api* URL is behind Mashery GW and uses the application(s) on https://apiconsole.cisco.com while

apx* URL is behind Mulesoft GW and uses the application(s) on https://anypoint.mulesoft.com/apiplatform/apx/#/portals

With having both in place and the correct permissions granted API access is working for CCW-R and Service APIs.