Skip to main content

​
How errors reach your AI client

  • Sign-in and limit errors stop the whole request. The server answers with an HTTP status, such as 401 or 429, and a JSON-RPC error with a plain message.
  • Refused tool calls come back as a tool result marked as an error. The text starts with the error code, for example insufficient_scope: This call needs the clients:write scope.
  • Invalid arguments come back as a JSON-RPC error, Invalid tool arguments, naming the argument that is not valid.
The codes are the same as the REST API’s. See errors.

​
Connecting

  • The client cannot connect, or reports 405. Use Streamable HTTP. In Claude Code, set the type to http, not sse. The server only accepts POST.
  • “This link cannot be used.” The app’s sign-in request was not valid, so Advisor will not send you back to it. Remove the connector and add it again.
  • “This request has expired or was already answered.” The consent page lasts 10 minutes and can be answered once. Start again from the app.
  • “You are not in a firm that can be connected.” You signed in with an account that is not in a firm. Sign in with your firm account.
  • The app is refused when it registers. Hosted apps must use a sign-in return address Advisor knows. Today that is Claude, ChatGPT, Cursor and VS Code, and any app that signs in through localhost. Contact support to have an app added, or use an API key.
  • Tools are missing. The tool list follows your access and your role. Connect again with Read and change for write tools. Admin-only tools need an admin. Restart the client after changing its settings.

​
401 Unauthorised

The credential is missing or no longer works. Your AI client shows one of these messages. To reconnect, remove or disconnect Redbark Advisor in your AI client, add it again and sign in. Connecting again replaces the old connection.

​
403 Forbidden

​
402 Subscription required

subscription_required means your firm needs a subscription to add clients, invite them or send checklists. Reading data still works. An admin can subscribe in Settings > Billing. See billing.

​
409 Client limit reached

client_limit_reached means all 20 active clients on your plan are in use. Archive a client you no longer work with (archive_client), or contact Redbark at support@redbark.com.

​
429 Too many requests

The connection or key made more than 120 requests in a minute. The message is “Too many requests. The limit is 120 a minute.”
  • Wait the number of seconds in the retry-after header, then try again.
  • The limit resets at the start of each minute.
  • You do not need to reconnect or make a new key.
To use fewer requests, ask for one client at a time, or ask your AI client to use the list tools’ limit and cursor rather than reading every item.

​
Other errors

  • 413, “Request body exceeds size limit.” A request can be up to 64 KB. Upload files with create_document_upload and the address it returns, not through a tool argument.
  • 400, “A batch holds 1 to 10 messages.” Send at most 10 JSON-RPC messages in one request.
  • Unknown tool. The tool name is wrong, or the client’s tool list is out of date. Restart the client.
  • invalid_cursor. Pass next_cursor back exactly as it was returned.
  • directory_unavailable. The team list could not be read. Try again in a moment.
  • 500, internal_error. Something went wrong on our side. Try again. If it keeps happening, contact support.

​
Getting help

Email support@redbark.com with the tool name, the error code and the time it happened. Do not send API keys, tokens or client data.