ToolbenchDocs
Get a key

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.

Agent skill file

Markdown instructions for an agent working this contractor account.

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

HTTPS event delivery (lead.created, lead.booked, review.created). Verify Toolbench-Signature on every POST.

Recipes

Text a contact, list callbacks, draft a review reply.

Changelog

REST v1 launched 18 September 2026.

Integration recipes

n8n, Zapier, signatures, MCP.

Step-by-step pages with copy buttons and tested verification code. All recipes.

Send new Toolbench leads to n8n

Register your n8n Webhook URL with POST /webhooks for lead.created, verify Toolbench-Signature in a Code node, then branch on the event payload.

Trigger a Zap from new Toolbench leads

Point POST /webhooks at a Webhooks by Zapier Catch Hook URL for lead.created — Zapier cannot verify Toolbench HMAC natively, so put verification on a small HTTPS proxy or accept only low-risk follow-ups until you add one.

Verify Toolbench webhook signatures

Read the raw body, parse Toolbench-Signature (t and v1), HMAC-SHA256 the string t + '.' + rawBody with the full whsec_… secret, then compare v1 in constant time and reject timestamps older than five minutes.

Use Toolbench in Claude or ChatGPT via MCP

Enable Settings → ChatGPT & Claude, paste the token into a custom MCP connector at https://app.toolbench.com/mcp, and ask in plain language — agents preview writes until you confirm.

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.

request
curl https://app.toolbench.com/api/v1/inbox?filter=callbacks \
  -H "Authorization: Bearer tb_cus_…"
Browse the reference

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.

mcp config
{
  "mcpServers": {
    "toolbench": {
      "url": "https://app.toolbench.com/mcp",
      "headers": {
        "Authorization": "Bearer tb_cus_…"
      }
    }
  }
}
Connect an agent

Your first call

Prove the token works.

terminal

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.

Your token

Held for this browser tab only. Closing the tab forgets it.

https://app.toolbench.com/api/v1/meNo token — send anyway to see 401
cURL
curl -X GET "https://app.toolbench.com/api/v1/me" \
  -H "Authorization: Bearer tb_cus_…"