Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Tempo request with API token => 401 unauthorized

Hi,

Yesterday, I tried to run a script to send timesheet to Tempo using the REST API.

I created a new API token and now I always get as response 401 Unauthorized. 

3-4 days ago, it was working fine and nothing have been changed in my code.

 

My request uses the bearer token authentification.

And calls 

POST https://api.tempo.io/core/3/worklogs

 

Was there any changes on the API side, like switching the authentification way?

Thanks.

1 answer

1 accepted

1 vote
Answer accepted

My bad >.>

Wrong API token...

All good, sorry.

 

You can close this.

Your API token is the one you generated in settings and not the OAuth2.0 token, isn't it? In that case, I am using the same, but still getting unauthorized error.

Like Fabio Fragapane likes this

Hello Manoj, did you find a solution for this ? I got the same error and the configuration hasn't changed. Could this be related to v3 or v4 of the api ?
Thanks

@Fabio Fragapane From another post I got the info that, to use the Token Authentication with API we have to use the following end point

https://api.tempo.io/4/worklogs

You can try this.

@Manoj Gnanaseelan Thanks Manoj. I had a different issue, the token was expiry. I refreshed it but it didn't work.

I had to re-create the configuration in the other tool (ServiceNow) and then the new token works.

Like Manoj Gnanaseelan likes this

@Fabio Fragapane Thanks for sharing. This might be useful for someone else facing similar issue.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events