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

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.

Lukasz Pater Atlassian Team Jun 12, 2014

Hi Brady,

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



Suggest an answer

Log in or Join to answer
Community showcase
Bridget Sauer
Published Mar 09, 2018 in Jira Service Desk

E.L. Fridge's take on education, Jira Service Desk, and creative Jira use cases

...word of mouth, so by 2016, we were working with several other entities on campus to implement Jira Service Desk . The Atlassian motto of “for every team” has really come true for us in this case. We...

339 views 0 9
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot