Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,367,634
Community Members
 
Community Events
168
Community Groups

REST API for commit hook fails with 401: not authorized

I followed this guide to create a curl command to trigger a scan of my respository:

I have verified multiple times that my API key is correct. I've also noticed that I get the same response when the repository name is changed from "sso" to something that doesn't exist.

I have a single repository named "sso" in my fisheye server.

curl -X POST -H "X-Api-Key: [my key was here]"  http://fisheye1/rest-service-fecru/admin/repositories-v1/sso/scan
{"code":"401","message":"You must be an administrator to access this resource.","stacktrace":null}

1 answer

1 accepted

0 votes
Answer accepted

I ended up adding another header

-H "Content-Type: application/json"

ANd it started working. I think the documentation needs to be updated because it doesn't specify this.

lpater Atlassian Team Jun 12, 2014

Hi Brady,

I've updated the docs to mention needing to add the content type.

Thanks,

Łukasz

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events