Toolbench API
Build on your shop's data.
One personal token. Call /api/v1 from your own scripts, or paste the same token into ChatGPT or Claude.
or
Start here
Pick a starting point.
Eight short guides. The quickstart gets you a working response in about two minutes.
Quickstart
Issue a token and prove GET /me in about two minutes.
Authentication
Bearer tb_cus_ on every call. One shop. Rotate to disconnect.
Agent reference
Same token in ChatGPT or Claude. Connect at /mcp — not REST.
Write access
REST writes go live. MCP still previews until you confirm.
Errors & limits
Stable codes, 120 requests a minute, Retry-After on 429.
Webhooks
Not in v1. Poll GET /inbox and GET /today instead.
Recipes
Text a contact, list callbacks, draft a review reply.
Changelog
REST v1 launched 18 September 2026.
The surface
What you can reach.
Every endpoint on REST v1, grouped. Each one has a live console on its reference page.
Two doors
Enable once. Use it either way.
Settings → API and Settings → ChatGPT & Claude issue the same tb_cus_ token. Rotate once and both disconnect.
Call it yourself
A plain REST API over HTTPS. Bearer header, JSON in, JSON out, limit paging. No SDK required.
curl https://app.toolbench.com/api/v1/inbox?filter=callbacks \
-H "Authorization: Bearer tb_cus_…"Hand it to an agent
Point ChatGPT or Claude at the MCP endpoint with the same token. Ask in plain language: what came in today, who hasn't been called back.
{
"mcpServers": {
"toolbench": {
"url": "https://app.toolbench.com/mcp",
"headers": {
"Authorization": "Bearer tb_cus_…"
}
}
}
}Your first call
Prove the token works.
Make the call right here
Paste your token and hit send. GET /me is read-only and changes nothing — it just proves the token works and tells you what's live on your shop.