Obsidian API Key

Ask the Community
1

I’m trying to set up Toggle 2.0 with the Obsidian plugin. It keeps telling me the API is unreachable. What do I do?

2

This automated response focused on the correct product that the plugin is built for by the developer, but it is misleading from the perspective of the user and what they are trying to set up. Please check the thread reply below for clarification and disregard this post.

That’s frustrating! Here are a few things worth checking:

First, make sure you are using the correct API token. You can find your Toggl Track API token by logging into Toggl Track, going to your Profile Settings, and scrolling to the bottom of the page where the API token is displayed.

Once you have confirmed the token is correct, try these steps:

  • Double-check that you are pasting the token without any extra spaces before or after it.
  • Make sure your Toggl Track account is active and that you can log in normally at toggl.com.
  • Try regenerating your API token in Profile Settings and then re-entering it in the Obsidian plugin.

If the issue persists, it is worth checking the Obsidian plugin’s own documentation or community forums, as the problem may be on the plugin’s side rather than with Toggl Track itself. Since this is a third-party plugin, Toggl Track does not control how it connects to the API, so the plugin maintainer would be the best resource for troubleshooting the connection error specifically.

— AI-generated response. Our team reviews all community posts. If you need further help feel free to tag Support in your reply.

3

Hi @ItsMeTho :waving_hand: stepping in here to clarify.

Thanks for posting and apologies, the automated reply above pointed you at Toggl Track, which isn’t what you’re setting up.

That Obsidian plugin was built for Toggl Track and doesn’t support Toggl 2.0. The “API is unreachable” message is misleading: the plugin shows it for any authentication failure, so nothing is actually down on our side. The two products just use different authentication, and the plugin only implements Track’s.

If you also use Toggl Track, the plugin will work with your Track API token from Toggl Track, though it will only see Track data.

For Toggl 2.0 support, the plugin developer would need to add it. The authentication docs are at Authentication | Toggl Engineering if you’d like to raise it with them.

Happy to help if anything else comes up.

Best,
Veljko