[Deepcast] doesn't recognise my DeepL API key
Extension
https://www.raycast.com/mooxl/deepcast
Raycast Version
1.83.2
macOS Version
14.7
Description
Deepcast reports that my DeepL API key is invalid. I attempted to reinstall the extensions, but it didn't help. I also tried using a new API key, but that didn't work either.
Steps To Reproduce
See my description.
Current Behaviour
No response
Expected Behaviour
No response
Thank you for opening this issue!
🔔 @mooxl @peter-gy @Popalay @MonsterDeveloper @YamenSharaf @EvanZhouDev @erics118 you might want to have a look.
💡 Author and Contributors commands
The author and contributors of mooxl/deepcast can trigger bot actions by commenting:
-
@raycastbot close this issueCloses the issue. -
@raycastbot close as not plannedCloses the issue as not planned. -
@raycastbot rename this issue to "Awesome new title"Renames the issue. -
@raycastbot reopen this issueReopens the issue. -
@raycastbot assign meAssigns yourself to the issue. -
@raycastbot good first issueAdds the "Good first issue" label to the issue. -
@raycastbot keep this issue openMake sure the issue won't go stale and will be kept open by the bot.
@peter-gy Hey, could you help me out with this, please?
It is still not working. Would appreciate you advice.
Your API key should look something like df4385c2-33de-e423-4134-ca1f7b3ea8b7 or with an additional :fx at the end of it. See https://support.deepl.com/hc/en-us/articles/360020695820-API-Key-for-DeepL-s-API
This issue has been automatically marked as stale because it did not have any recent activity.
It will be closed if no further activity occurs in the next 10 days to keep our backlog clean 😊
It' the same for me. It is not working with my "DeepL API Free" key.
This issue has been automatically marked as stale because it did not have any recent activity.
It will be closed if no further activity occurs in the next 10 days to keep our backlog clean 😊
This issue has been automatically closed due to inactivity.
Feel free to comment in the thread when you're ready to continue working on it 🙂
You can also catch us in Slack if you want to discuss this.