Workspace ID, API key, tool token & console
What each credential on the Connections screen is for — your workspace ID, the API key, the tool token behind the record tools, and console access — and which ones you actually need.
The Connections screen (agent4.io/dashboard/tenant) gathers the technical handles for your workspace. Most people never need them — they exist for wiring agent4.io into your own software. Here is what each one is.
Workspace ID
A stable identifier for your workspace (your "tenant"). It is not secret; it just tells the platform which workspace's agents, data and usage a request belongs to. You rarely type it yourself.
API key
Your workspace's secret key for the platform API. Use it when your own code or a third-party tool calls agent4.io directly — for example a custom app that talks to your agent. Treat it like a password: keep it server-side, never paste it into a browser or a public repo. Details in Authentication.
Tool token
The credential your agents authenticate with when they file a record — the leads, bookings, checklists and escalations that land in your Inbox. Agents the setup wizard created are already connected, so you normally never touch this. You only need it if you are wiring the record tools into something of your own.
It is a secret, not a public key: anyone holding it can file records into your Inbox, so keep it server-side and never paste it into a browser, front-end code or a public page. It is not meant to be exposed in a website widget.
Console access
The console is the full admin panel for your workspace, where you can manage every agent, knowledge base and skill in one place. You reach it from the dashboard without signing in again — agent4.io is the console's identity provider, so it is a click, not a second login. You can also set a console password here as a fallback way in, in case you ever need to reach the console when the dashboard is unavailable. Open it any time at agent4.io/console/enter.
Which do I actually need?
- Just building agents in the dashboard? None of these — the wizard wires everything for you.
- Putting the widget on your site? See Embed the web widget; you paste a share snippet, not your API key.
- Calling agent4.io from your own backend? That is what the API key is for.