Skip to main content
When a tool call fails, Alura returns an error your assistant can read: a code, a suggestion and whether to retry (retryable), plus retry_after_seconds when waiting helps. Most assistants act on it by themselves. This page is for when they can’t. Every code links to its page in Errors.

Sign-in and 401 errors

Alura answers 401 with a WWW-Authenticate header, and the assistant should start the sign-in again. It happens when:
  • The connection was disconnected, in Settings > Connected apps, or a workspace owner removed its last workspace.
  • It wasn’t used for 30 days. Access lasts 15 minutes and the assistant renews it by itself, but the renewal expires after 30 days without use.
  • The account was suspended.
To reconnect:
  • Claude.ai and Claude Desktop: Customize > Connectors, then Connect next to Alura.
  • Claude Code: run /mcp, pick alura and sign in. If that doesn’t help, claude mcp remove alura and add it again.
  • ChatGPT and Cursor: open the Alura plugin or server and connect again.
Sign-ins from an assistant work only on https://mcp.alura.io/mcp. Scripts calling https://api.alura.io/v1 need an API key.
The key was revoked, rotated more than 24 hours ago, or mistyped. Check it in Settings > API and send it as Authorization: Bearer alura_sk_....

The approval screen

When Alura creates a Free workspace for a new account, it also checks the email address:

Tools are missing or refused

The assistant sees only tools for the permissions you allowed on the approval screen. For example, without Save research for you there is no add_to_saved_list. To change permissions, disconnect in Settings > Connected apps and connect again. Tools lists which permission each tool needs.list_workspaces and switch_workspace appear only if you’re in more than one workspace.In a ChatGPT workspace, ChatGPT keeps the tool list from when the plugin was published; an admin uses Refresh in the workspace’s app settings to pick up new tools. On ChatGPT Pro, only tools that read are available, so saving research isn’t.
A tool was called without its permission, usually because the assistant remembered it from an earlier connection. Connect again and allow the permission.
Sales history and keyword search history need the Growth plan or above. The refusal is free. Over MCP it says the plan is managed in Alura’s settings, without a link; the workspace’s owners can change it under Settings > Plans. Saving items also depends on the plan: Free workspaces can read saved research but not add to it.

Workspaces

The connection has no current workspace, usually because you left it or an owner removed the app from it. Ask the assistant to list your workspaces and switch to one (“Switch Alura to my Wholesale workspace”). If you have no workspace left, the connection is revoked: connect again.
Each connection keeps its own current workspace, chosen on the approval screen. Switching workspace in the Alura app doesn’t change it. Ask “Which Alura workspace are you working in?”, then ask it to switch. A switch applies to every chat on that connection.
Saved research belongs to a workspace, so lists in another workspace appear after a switch. Private lists appear only to the person who created them. Global and public lists from the Alura app are not available over MCP.
A page cursor works only in the workspace that produced it. After a switch, ask for the list again from the first page.

Limits

Rate and fetch limits has the numbers per plan.

Pending items

For now, Alura answers only with products, shops and keywords it already has. One it hasn’t seen answers fetch_unavailable, free. In a batch, the items Alura has come back in the results and the rest are listed in unfetched, each with a code and retry_after. Only returned items are charged. When Alura starts fetching new items from Etsy on request, the server will wait up to 20 seconds for a product or keyword. If it isn’t ready, or it’s a shop, which takes minutes, the tool will answer with "status": "pending", retry_after_seconds and a suggestion to call again with the same arguments, free. Batches will list those items in pending.

Still stuck

Every tool result carries a request_id in _meta. Send it to Alura support from the app, with the time and the assistant you used.