Skip to content

Get the current account

GET /public/v1/me

Tells you who a credential acts for: the organization, and, for an OAuth token, the person who approved your app. Where check your credentials only confirms that a credential works, this names the account behind it. It takes no parameters, changes nothing, and is not throttled.

The CLI has no command for it, and the MCP server has no tool for it.

With an API key:

Terminal window
curl -H "Authorization: your-api-key" \
https://dash.sharek.app/api/public/v1/me

With an OAuth token:

Terminal window
curl -H "Authorization: pos_your_oauth_token" \
https://dash.sharek.app/api/public/v1/me

With an API key, user is null:

{
"organization": { "id": "organization-id", "name": "Acme Agency" },
"user": null
}

With an OAuth token, user is the person who approved your app:

{
"organization": { "id": "organization-id", "name": "Acme Agency" },
"user": {
"id": "user-id",
"name": "Jane Doe",
"picture": "https://media.example.com/a1b2c3d4e5.png"
}
}
Field Description
organization.id The organization the credential acts for. For an OAuth token, the same value as id in the token exchange response.
organization.name That organization’s name.
user null for an API key, which belongs to the whole organization rather than to one person. For an OAuth token, the person who approved your app on the consent screen.
user.id That person’s id.
user.name Their name, or null if none is set.
user.picture The address of their profile picture, or null if they have none.
  • The natural call after the OAuth exchange. The token response tells you which organization you reached; this call adds who connected it, so your product can show something like “Connected as Jane Doe, Acme Agency”.
  • To know which person is calling, use an OAuth token. An API key answers for the whole organization, so it never reports one (see authentication).
  • This call is not throttled; only creating posts is (see rate limits).
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.