How to Get Monday.com API Key Easily 2026

Click your avatar in the top-right corner of any Monday.com workspace to open the account panel. It's split into two columns: Account on the left, with items like My profile, Developers, and Administration, and Explore on the right, with the app marketplace and mobile app links. Which of those two Account items you need, Developers or Administration, depends on your role, which the next step covers.

If you are not an account admin, click Developers in the avatar menu. It opens the Developer Center in a new tab; from there, click API token, then Show, to reveal your personal token.

If you are an account admin, you have a second route: Administration in the same avatar menu, then Connections in the left sidebar, then Personal API token. That's the screen shown here, with a single input labeled Personal API Token, a Generate link, and a Copy button.

A blue note links to the API documentation, and a red banner warns that the token grants powerful access to your account, so treat it like a password. Both routes point at the same personal token, tied to your own user account rather than to a board or workspace.

With the field empty, click Generate (or Show, on the Developers path, once a token already exists). Monday.com fills the box with a long signed string, your personal token, tied to your user account and its permission level, not to a specific board or workspace.

Click Copy right away and paste it straight into wherever it needs to live: an environment variable, a secrets manager, or the header of your script. Don't leave it sitting in a chat message or a plain text file. Move it into secure storage before doing anything else with it.

A personal API token inherits your own user permissions across the account. If you can see a board, edit an item, or manage automations manually, your token can do the same thing through the API.

This is different from an OAuth app credential, which is scoped to whatever permissions a user explicitly grants during an install flow. For a personal script or a local automation agent only you will run, the personal token is the simpler path. For anything you plan to distribute to other users or connect on their behalf, look at building an OAuth app instead, so you're not handing out access tied to your own account.

Before wiring the token into a larger workflow, send one simple authenticated request to Monday.com's GraphQL API endpoint. A query for your own account name or user ID is enough to confirm the token works and that you're pointed at the right API URL. Catching an authentication problem at this stage, with one request, is far faster than debugging it inside a half-built integration with multiple moving parts.

If a token ends up somewhere it shouldn't, committed to a public repository, pasted into a shared document, or used in a script that got copied around, go back to the same token screen and click Generate again. Monday.com issues a fresh token and immediately invalidates the old one, which cuts off anything still using it. Update every place that referenced the old token afterward, since regenerating breaks those connections until you swap in the new value, and check your workspace's activity log for anything that looks like it came from the compromised key.