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.

Thanks,

Łukasz

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published Monday in Jira Software

How large do you think Jira Software can grow?

Hi Atlassian Community! My name is Shana, and I’m on the Jira Software team. One of the many reasons this Community exists is to connect you to others on similar product journeys or with comparabl...

574 views 6 12
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