Check your credentials
GET /public/v1/is-connectedAnswers one question: is this credential good? It takes no parameters, changes nothing, and is not throttled, which makes it the right call for a health check or the first thing to run when you are setting up. To see who the credential acts for, get the current account.
The CLI’s closest equivalent is sharek auth:status, which
checks the credentials the CLI is using; the MCP server has no tool for it.
Request
Section titled “Request”curl -H "Authorization: your-api-key" \ https://dash.sharek.app/api/public/v1/is-connectedResponse
Section titled “Response”{ "connected": true }The value is always true. A bad credential never reaches this response; it is refused
with 401 before the operation runs, so treat any 200 as success and read the status
code rather than the field.
Failures
Section titled “Failures”| Response | Meaning |
|---|---|
401 {"msg": "No API Key found"} |
No Authorization header was sent. |
401 {"msg": "Invalid API key"} |
The key is not recognised. A Bearer prefix is the usual cause. |
401 {"msg": "Invalid OAuth token"} |
A pos_ token that is revoked or unknown. |
401 {"msg": "No subscription found"} |
The credential is valid but the organization has no active subscription. |
Details on each are on authentication.