# API 401 No credentials found for given claim 'iss' **URL:** \ **Category:** Developer Forum\ **Created:** [19. Februar 2024 um 09:42 UTC](https://community.awork.com/t/api-401-no-credentials-found-for-given-claim-iss/483 "2024-02-19T09:42:31Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![Philipp.P](https://avatars.discourse-cdn.com/v4/letter/p/d26b3c/32.png) [@Philipp.P](https://community.awork.com/u/Philipp.P)\ **Post date:** [19. Februar 2024 um 09:42 UTC](https://community.awork.com/t/api-401-no-credentials-found-for-given-claim-iss/483/1 "2024-02-19T09:42:31Z")
Dear sir or madam, we are using your provided API for various integrations for the last ~2 years as documented in [https://developers.awork.com/](https://developers.awork.com/), from today our requests don’t work at all any more, due to an unauthorised error response, on our side nothing has been changed and we double-checked our implementation. As example reponse to our request, e.g. `GET /api/v1/timeentries?orderby=startDateLocal%20desc,startTimeLocal%20desc&grouping=user&page=1&pageSize=1000` we do receive a response with status code 401 and body `No credentials found for given claim 'iss'`. We do use the api-key authorization method as described in your documentation. Of course we double-checked we are using the `.com` awork domain. We are looking forward to prompt feedback to continue using our tools and integrations. Kind regards Philipp ---
**Author:** ![Chris](https://dub1.discourse-cdn.com/flex013/user_avatar/community.awork.com/chris/32/1029_2.png) [@Chris](https://community.awork.com/u/Chris)\ **Post date:** [19. Februar 2024 um 10:16 UTC](https://community.awork.com/t/api-401-no-credentials-found-for-given-claim-iss/483/2 "2024-02-19T10:16:03Z")
Same here: /api/v1/projects ![Screenshot 2024-02-19 111538](https://europe1.discourse-cdn.com/flex013/uploads/awork1/original/1X/f55500d6164721328319fb0fdab553709127190f.png) ---
**Author:** ![Marcello](https://dub1.discourse-cdn.com/flex013/user_avatar/community.awork.com/marcello/32/131_2.png) [@Marcello](https://community.awork.com/u/Marcello)\ **Post date:** [19. Februar 2024 um 12:34 UTC](https://community.awork.com/t/api-401-no-credentials-found-for-given-claim-iss/483/3 "2024-02-19T12:34:27Z")
> [@Philipp.P](#): > > ed API for various integrations for the last ~2 years as documented in [https://developers.awork.com/](https://developers.awork.com/), from today our requests don’t work at all any more, due to an unauthorised error response, on our side nothing has been changed and we double-checked our implementation. As example reponse to our request, e.g. `GET /api/v1/timeentries?orderby=startDateLocal%20desc,startT` Hi @Philipp.P, thanks for the message. Have you tried to generate a new api token? Could you as well check if the token that you’re using is older than September 2023? In that case, I can confirm that you have to generate a new one. Hope that this will fix your issues. ---
**Author:** ![Philipp.P](https://avatars.discourse-cdn.com/v4/letter/p/d26b3c/32.png) [@Philipp.P](https://community.awork.com/u/Philipp.P)\ **Post date:** [19. Februar 2024 um 12:59 UTC](https://community.awork.com/t/api-401-no-credentials-found-for-given-claim-iss/483/4 "2024-02-19T12:59:42Z")
Yes I have already tried that, the same issue occurred. ---
**Author:** ![vitor](https://dub1.discourse-cdn.com/flex013/user_avatar/community.awork.com/vitor/32/195_2.png) [@vitor](https://community.awork.com/u/vitor)\ **Post date:** [19. Februar 2024 um 13:01 UTC](https://community.awork.com/t/api-401-no-credentials-found-for-given-claim-iss/483/5 "2024-02-19T13:01:51Z")
Hello! Could someone please share a trace id of a request with us? Thanks! ---
**Author:** ![Chris](https://dub1.discourse-cdn.com/flex013/user_avatar/community.awork.com/chris/32/1029_2.png) [@Chris](https://community.awork.com/u/Chris)\ **Post date:** [19. Februar 2024 um 13:06 UTC](https://community.awork.com/t/api-401-no-credentials-found-for-given-claim-iss/483/6 "2024-02-19T13:06:36Z")
Thank you @Marcello Everything is working again for us now! 👍 ---
**Author:** ![vitor](https://dub1.discourse-cdn.com/flex013/user_avatar/community.awork.com/vitor/32/195_2.png) [@vitor](https://community.awork.com/u/vitor)\ **Post date:** [19. Februar 2024 um 13:29 UTC](https://community.awork.com/t/api-401-no-credentials-found-for-given-claim-iss/483/7 "2024-02-19T13:29:33Z")
@Philipp.P if you are still having issues after generating a new token, please let us know and, if possible, share with us a trace id of the request. @Chris awesome! We are glad to help. ---
**Author:** ![Philipp.P](https://avatars.discourse-cdn.com/v4/letter/p/d26b3c/32.png) [@Philipp.P](https://community.awork.com/u/Philipp.P)\ **Post date:** [19. Februar 2024 um 14:03 UTC](https://community.awork.com/t/api-401-no-credentials-found-for-given-claim-iss/483/8 "2024-02-19T14:03:18Z")
Thank you @vitor I generated another api-key and its working with that. I also tried finding a trace id of a failing request but couldn’t see it included. ---
**Author:** ![vitor](https://dub1.discourse-cdn.com/flex013/user_avatar/community.awork.com/vitor/32/195_2.png) [@vitor](https://community.awork.com/u/vitor)\ **Post date:** [19. Februar 2024 um 14:19 UTC](https://community.awork.com/t/api-401-no-credentials-found-for-given-claim-iss/483/9 "2024-02-19T14:19:44Z")
If you are getting the following error when using our API: `{"message":"No credentials found for given claim 'iss'"}`, please issue a new token so they are compatible with the new [awork.com](http://awork.com/) domain. Best regards, Vitor Durante. ---
**Author:** ![Sebastian](https://dub1.discourse-cdn.com/flex013/user_avatar/community.awork.com/sebastian/32/1305_2.png) [@Sebastian](https://community.awork.com/u/Sebastian)\ **Post date:** [19. Februar 2024 um 16:39 UTC](https://community.awork.com/t/api-401-no-credentials-found-for-given-claim-iss/483/10 "2024-02-19T16:39:00Z")
Just to follow up on this, here are more details about the domain change and breaking changes for API and SSO Integrations, as announced in September 2023: [awork switches to .com | awork Helpcenter](https://support.awork.com/en/articles/8333169-awork-switches-to-com) If you have not received those updates, I recommend signing up for our API and Developer Newsletter, where we communicate changes like this: [https://developers.awork.com/](https://developers.awork.com/)