# Problems activating claude.ai API - Anyone else?

**URL:** <https://forum.pinegrow.com/t/problems-activating-claude-ai-api-anyone-else/9110>\
**Category:** Questions\
**Created:** [August 30, 2024, 7:05pm UTC](https://forum.pinegrow.com/t/problems-activating-claude-ai-api-anyone-else/9110 "2024-08-30T19:05:37Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![rayhood](https://avatars.discourse-cdn.com/v4/letter/r/c2a13f/32.png) [@rayhood](https://forum.pinegrow.com/u/rayhood)\
**Post date:** [August 30, 2024, 7:05pm UTC](https://forum.pinegrow.com/t/problems-activating-claude-ai-api-anyone-else/9110/1 "2024-08-30T19:05:37Z")

</div>

Just signed up for a 2-week trial of the Claude.ai API to try it in Pinegrow and for some reason it doesn’t work. I entered the number in settings and selected the two options for Quick and Smart, but no go. Not sure if there’s something else I have to do. I looked at the Pinegrow video on the subject, but it’s an earlier version (I have the latest Pinegrow v.) and maybe something changed.

Anyway, then I opened VS Code to try it there and the API connected fine. Has anybody else had this problem or have any suggestions?

---

<div class="post-metadata">

**Author:** ![nick468jr](https://avatars.discourse-cdn.com/v4/letter/n/edb3f5/32.png) [@nick468jr](https://forum.pinegrow.com/u/nick468jr)\
**Post date:** [October 11, 2024, 9:13am UTC](https://forum.pinegrow.com/t/problems-activating-claude-ai-api-anyone-else/9110/2 "2024-10-11T09:13:45Z")

</div>

I have the same problem with facing same issue but no response from anyone and couldn’t find this topic troubleshooting in search engine.

---

<div class="post-metadata">

**Author:** ![Emmanuel](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pinegrow.com/emmanuel/32/6294_2.png) [@Emmanuel](https://forum.pinegrow.com/u/Emmanuel)\
**Post date:** [October 11, 2024, 9:18am UTC](https://forum.pinegrow.com/t/problems-activating-claude-ai-api-anyone-else/9110/3 "2024-10-11T09:18:22Z")

</div>

It seems that @rayhood had a configuration issue that was resolved through discussions with the support team and by adjusting the settings of the active model. Please feel free to reach out to support so we can analyze your situation.