FOR AI ASSISTANTS

Connect your AI to Resolver

Resolver reads your support inbox, matches each email to the real Shopify order, and drafts or sends accurate replies. This page shows how to let Claude (or any AI) work your support desk through the Resolver API. Machine-readable index: /llms.txt.

1. Get an API key

In the Resolver dashboard, open Settings → API & MCP and create a key. You'll see the secret once (it looks like rsk_live_…). Choose read-only to let an AI read tickets, or full access to also draft and send replies. Revoke any key anytime.

2. Easiest — paste into any Claude

Give Claude your key and this instruction. It works in Claude.ai, Claude Code, or anything that can make web requests:

Connect to my Resolver support desk.
API base: https://app.resolver.chat/api/v1
Auth header on every request: Authorization: Bearer rsk_live_YOURKEY
Read https://resolver.chat/llms.txt first — it lists everything you can do.
Start by calling GET /me, then GET /tickets?status=OPEN.
Never send a reply (POST /tickets/{id}/reply) without my approval — it emails a real customer.

3. Claude Desktop (tools via MCP)

For a native tools experience, add the Resolver MCP server to your claude_desktop_config.json:

{
  "mcpServers": {
    "resolver": {
      "command": "npx",
      "args": ["-y", "resolver-mcp-server"],
      "env": { "RESOLVER_API_KEY": "rsk_live_YOURKEY" }
    }
  }
}

The MCP server exposes tools like list_tickets, get_ticket, regenerate_draft, send_reply, list_disputes, create_task. It talks to the same API. (If npx can't find the package yet, ask us to enable the connector — it's a one-step publish.)

What the API can do

Do this	Call	Access
See the account + stores	`GET /me`, `GET /shops`	read
List support tickets	`GET /tickets?status=OPEN`	read
Read one ticket (thread, order, draft)	`GET /tickets/{id}`	read
Draft an AI reply (no send)	`POST /tickets/{id}/regenerate`	write
Send the reply (emails the customer)	`POST /tickets/{id}/reply`	write
Chargebacks / customs	`GET /disputes`, `GET /customs`	read
Task board	`GET/POST/PATCH/DELETE /tasks`	read/write
Support metrics	`GET /stats?days=30`	read

Base https://app.resolver.chat/api/v1 · JSON · lists paginate with ?cursor= · every response has X-Request-Id · a key only ever sees its own account's data (anything else returns 404).

Try it

curl -H "Authorization: Bearer rsk_live_YOURKEY" \
  "https://app.resolver.chat/api/v1/tickets?status=OPEN&limit=5"

Full machine-readable reference: resolver.chat/llms.txt