cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
515
Views
0
Helpful
3
Replies

Access to Services API Contracts

cfainer01
Level 1
Level 1

i apparently have access to the contracts Services API, as i can now connect to the URL https://apx.cisco.com/cs/api/v1/customer-info/customer-details and not get access denied.  But now, im getting {"message":"Bad Request. Please check the HTTP method.","error":"org.mule.module.apikit.exception.MethodNotAllowedException"} when i try and access https://apx.cisco.com/cs/api/v1/customer-info/customer-details.  I dont see any required fields to post in the header in the docs.  does anyone have this working?  am i missing some permission still?

3 Replies 3

Just based on the error output and the error message {"message":"Bad Request. Please check the HTTP method.","error":"org.mule.module.apikit.exception.MethodNotAllowedException"}  Would means that the HTTP method that you are using is not allowed for the specified URL.
 
For example if you used the POST method to try and access the URL https://apx.cisco.com/cs/api/v1/customer-info/customer-details, but the only allowed methods for this URL are GET and OPTIONS.
 
Hope this helps.
Please mark this as helpful or solution accepted to help others
Connect with me https://bigevilbeard.github.io

thank you... nice catch.  overlooked the obvious.

for the get, i got

{
    "data": []
}
 
when i search for a specific customerid via https://apx.cisco.com/cs/api/v1/customer-info/inventory-groups?customerId=, using a customer ID i can get from the PSS APIs, i get
{
    "status": 403,
    "message": "Invalid input request",
    "reason": {
        "errorCode": "API_PARTY_002",
        "errorInfo": "Customer Id is not associated with Partner"
    }
}
 
i guess im discouraged...  i cant find any docs for the PSS APIs for contracts anymore... they all point to the services API docs, which i cant seem to get data from.

The docs are located at devnet I think this is what you are looking for https://developer.cisco.com/docs/support-apis/#!user-onboarding-process/user-onboarding-process

After that I would double check your user account has access and the correct role permissions, as that’s normally why you get the 403. 

Hope this helps.

 

Please mark this as helpful or solution accepted to help others
Connect with me https://bigevilbeard.github.io