Skip to content

API overview

The Sharek public API schedules posts, manages channels, uploads media and pulls analytics over HTTP. Most of what you do on the calendar, you can do from a script.

Every operation on these pages sits under one prefix:

https://dash.sharek.app/api/public/v1

So listing your channels is a GET to https://dash.sharek.app/api/public/v1/integrations.

Two ids come up constantly and are easy to confuse:

  • Integration id identifies a connected channel. You get it from list channels, or from Copy Channel ID in the channel menu in the app.
  • Post id and group identify a scheduled post. One call to create a post across three channels creates three posts, each with its own id and group. A post’s replies share its group, which is what delete a post group takes.

Send your key in the Authorization header with no scheme prefix:

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

A successful call answers {"connected": true}. Where the key comes from, what the pos_ OAuth tokens are, and what each failure looks like are on authentication.

One operation is throttled: create a post, at 100 requests per hour per organization. Everything else is unthrottled.

That is 100 requests, not 100 posts. A single create call can carry many channels and many posts, so batch rather than loop when you are scheduling in bulk. Exceeding the limit returns 429.

  • Dates are UTC, ISO 8601, for example 2026-09-01T10:00:00.000Z.
  • JSON bodies are capped at about 100 kb. This is small on purpose: media never travels inline. Upload it first with upload a file or upload from a URL, then reference what those return.
  • The API is for server-side use. Cross-origin browser requests are refused: a preflight from an unrelated origin comes back without an allowed-origin header. Call it from your backend, a script, or the CLI, and keep your key off the client.

Sharek returns five different JSON error shapes depending on which layer rejected the request. Handle all five if you are writing a client.

Source Status Shape
Controller errors 400, 401, 404, 500 {"msg": "..."}
Post validation on create 400 {"statusCode": 400, "provider": "...", "name": "...", "message": "..."}
Quota or subscription 402 {"statusCode": 402, "message": "...", "url": "...", "section": "...", "resetsAt": "..."}
Field validation 400 {"statusCode": 400, "message": ["..."], "error": "Bad Request"}
Lookups, service checks and the throttle 400, 404, 406, 422, 429, 500 {"statusCode": 404, "message": "Post not found", "error": "Not Found"}

In the last shape message is a single string, and error is sometimes absent: a missing media item answers {"statusCode": 404, "message": "Media not found"}, the throttle answers 429 with "message": "ThrottlerException: Too Many Requests", and an unexpected server error answers 500 with "message": "Internal server error".

Update post settings runs the same checks but answers in the last shape, with the channel name at the start of message.

The 402 shape is the one worth special-casing. It means the organization hit a plan limit rather than sending a bad request, and its url points at where to resolve it.

  • Authentication to get a key and make the first call.
  • OAuth apps if you are building a product that acts on behalf of other Sharek accounts.
  • Get the current account to see which organization, and with an OAuth token which person, a credential acts for.
  • Create a post is the operation most clients are really after, and the one with the largest request body.
  • Start a channel connection to let someone connect a channel from your product.
  • List notifications to pick up publishing failures and channels that need reconnecting.
  • Automate with n8n if a community node in a workflow would save you writing a client at all.