Platforms
What we support, and how we use each API.
Lemmek uses each platform's official API for one purpose: publishing content on behalf of a user who connected their own account and gave consent through the platform's login screen.
What we do
- Publish posts, videos and images that the user, or an app acting on their instruction, asks to publish.
- Read the basic profile of the connected account (id, name, avatar) so the user can recognise it.
- Check the status of posts we published, to confirm they went live and report a link.
What we never do
- Read or send private messages, follow, like or comment on behalf of users.
- Collect follower lists, audience data or content from other accounts.
- Sell platform data, use it for advertising, or share it beyond what is needed to publish.
- Automate fake engagement or help anyone get around platform rules or limits.
In review our app has been or is being submitted for the platform's review and is not yet available to the public.Coming soon planned for the beta; no public access yet.
Social video
TikTok
Coming soon- API
- TikTok Login Kit and Content Posting API
- What we publish
- Videos and photo posts to the connected creator account, either posted directly or sent to the creator's TikTok inbox as a draft to finish in the app.
- Accounts
- Personal and business TikTok accounts that the creator connects themselves.
- Permissions requested
user.info.basic, video.publish, video.upload- Notes
- Before every post we query the creator's current posting options (creator_info). Privacy level is always chosen explicitly by the creator; there is no default. Commercial content and AI-generated content disclosures are passed through as the creator sets them.
- Platform terms
- TikTok Terms of Service
YouTube
Coming soon- API
- YouTube Data API v3
- What we publish
- Video uploads, including Shorts, with title, description, privacy status, made-for-kids and altered or synthetic content settings chosen by the channel owner.
- Accounts
- YouTube channels owned or managed by the Google account that connects.
- Permissions requested
https://www.googleapis.com/auth/youtube.upload, https://www.googleapis.com/auth/youtube.readonly- Notes
- Read-only access is used only to identify the connected channel and confirm that an uploaded video exists and has finished processing.
- Platform terms
- YouTube Terms of Service
Social
- API
- Instagram API with Instagram Login, or with Facebook Login for Business
- What we publish
- Reels, feed images, carousels and stories to Instagram professional (business or creator) accounts.
- Accounts
- Instagram professional accounts only. Personal accounts cannot be connected.
- Permissions requested
instagram_business_basic, instagram_business_content_publish (Instagram Login); instagram_basic, instagram_content_publish, pages_show_list (Facebook Login for Business)- Notes
- We do not read or send direct messages, do not follow, like or comment on behalf of users, and do not collect follower data.
- Platform terms
- Meta Platform Terms
Facebook Pages
Coming soon- API
- Facebook Graph API (Pages) via Facebook Login for Business
- What we publish
- Text, link, photo and video posts and reels to Facebook Pages the user manages and explicitly selects during connection.
- Accounts
- Facebook Pages only. We never post to personal profiles or groups.
- Permissions requested
pages_show_list, pages_manage_posts, pages_read_engagement- Platform terms
- Meta Platform Terms
Threads
Coming soon- API
- Threads API
- What we publish
- Text, image, video and carousel posts to the connected Threads profile.
- Accounts
- Threads profiles connected by their owner.
- Permissions requested
threads_basic, threads_content_publish- Platform terms
- Meta Platform Terms
- API
- LinkedIn Posts API; Community Management API for Company Pages
- What we publish
- Text, image, document and video posts to the member's own profile, or to Company Pages where the member is an administrator.
- Accounts
- LinkedIn members and the Company Pages they administer.
- Permissions requested
openid, profile, w_member_social; organization posting permissions for Company Pages- Platform terms
- LinkedIn API Terms of Use
- API
- Pinterest API v5
- What we publish
- Image and video Pins to boards the user owns and selects.
- Accounts
- Pinterest business and personal accounts connected by their owner.
- Permissions requested
user_accounts:read, boards:read, pins:read, pins:write- Platform terms
- Pinterest Developer Guidelines
X
Coming soon- API
- X API v2 using the customer's own developer app and keys
- What we publish
- Posts with text, images and video to the connected X account.
- Accounts
- X accounts connected through the customer's own X developer app.
- Permissions requested
tweet.read, tweet.write, users.read, media.write, offline.access- Notes
- X access is available only with the customer's own API keys. API usage is billed by X directly to the customer.
Bluesky
Coming soon- API
- AT Protocol (OAuth or app password)
- What we publish
- Posts with text, images, video and link cards to the connected Bluesky account.
- Accounts
- Bluesky accounts on bsky.social or any compatible PDS.
- Permissions requested
Repository write access for posts and media (atproto OAuth), or an app password the user creates and can revoke at any time.
Fediverse & open protocols
Mastodon
Coming soon- API
- Mastodon client API (OAuth 2.0 with PKCE), also spoken by Pixelfed, GoToSocial and Akkoma/Pleroma
- What we publish
- Posts with text and media to the connected account on the user's own server.
- Accounts
- Accounts on any Mastodon-compatible server (Mastodon, Pixelfed, GoToSocial, Akkoma/Pleroma) that the user names themselves; we register a client app with that server on connection.
- Permissions requested
read:accounts, read:statuses, write:statuses, write:media
Misskey (and Sharkey, Firefish)
Coming soon- API
- Misskey API via MiAuth
- What we publish
- Notes with text and drive files to the connected account on the user's own server.
- Accounts
- Accounts on any Misskey-compatible server (Misskey, Sharkey, Firefish) that the user names themselves.
- Permissions requested
read:account, write:notes, write:drive
PeerTube
Coming soon- API
- PeerTube REST API
- What we publish
- Video uploads to channels on the connected account's own PeerTube server.
- Accounts
- Accounts on any PeerTube server that the user names themselves.
- Permissions requested
Full account access via a session token, not a password.- Notes
- The user pastes a token copied from their own logged-in PeerTube session. Lemmek exchanges it right away for its own access and refresh tokens and keeps the session alive by refreshing them; it never takes the account password.
Lemmy
Coming soon- API
- Lemmy API v3 (Lemmy 0.19)
- What we publish
- Text, link and single-image posts to communities on the connected account's own Lemmy server.
- Accounts
- Accounts on any Lemmy server that the user names themselves.
- Permissions requested
Full account access via a login token, not a password.- Notes
- The user pastes their login token (the jwt of their own browser session) to connect; Lemmek never takes a password.
Nostr
Coming soon- API
- Nostr protocol (NIP-46 remote signing, NIP-01 notes)
- What we publish
- Text notes (kind 1) sent to the relays listed in the user's own NIP-65 relay list, with media uploaded to the user's Blossom server when they have one.
- Accounts
- Any Nostr identity reachable through a NIP-46 remote signer.
- Permissions requested
Signing of kind 1 notes and Blossom media uploads, granted to Lemmek's own client key by the user's remote signer.- Notes
- The user pastes a bunker:// link from their own NIP-46 signer app; their private key never reaches Lemmek, only a client key for that link is stored. NIP-44 signers only; nostrconnect:// and auth_url approval flows are not supported yet.
Chat & communities
Telegram channels
Coming soon- API
- Telegram Bot API
- What we publish
- Messages with text, images and video to public or private channels where the channel owner has added our bot as an administrator with the right to post.
- Accounts
- Telegram channels administered by the user. We do not send messages to individual users or groups.
- Permissions requested
Channel administrator right: post messages. The owner can remove the bot at any time.
Matrix
Coming soon- API
- Matrix Client-Server API
- What we publish
- Messages with text, images and video to a room, sent by the shared Lemmek bot account.
- Accounts
- Any Matrix room whose owner invites the Lemmek bot and proves control by posting a one-time code in the room.
- Permissions requested
Bot account access: joining the room and sending m.room.message events.- Notes
- End-to-end encrypted rooms are not supported; the bot cannot post into them.
Discord
Coming soon- API
- Discord API (bot via OAuth2), or an incoming webhook
- What we publish
- Messages with text and up to 10 files to a channel.
- Accounts
- Discord servers where a user with the Manage Server permission adds the Lemmek bot, or creates a channel webhook.
- Permissions requested
View Channel, Send Messages, Embed Links, Attach Files, Read Message History (bot); or a channel webhook URL pasted by the user.
Slack
Coming soon- API
- Slack Web API (OAuth v2)
- What we publish
- Messages with text and up to 10 files to a channel.
- Accounts
- Slack workspaces where a workspace admin installs the Lemmek app; it posts as its own bot user.
- Permissions requested
chat:write, files:write, channels:read, groups:read, channels:join, channels:history, groups:history- Notes
- Private channels need an explicit /invite of the Lemmek bot before it can post there.
Viber channels
Coming soon- API
- Viber Channels Post API
- What we publish
- Text, picture, video and link messages to a channel.
- Accounts
- Viber channels whose super admin connects them.
- Permissions requested
Posting as the channel, via a channel token.- Notes
- The super admin pastes the channel's token from Channel > Settings > Developer tools, not a password. Viber requires a webhook on the channel before it accepts posts; Lemmek sets one automatically if the channel has none.
LINE Official Account
Coming soon- API
- LINE Messaging API
- What we publish
- Broadcast messages with text and up to 4 images or videos, sent to every follower of the account.
- Accounts
- LINE Official Accounts whose owner connects them.
- Permissions requested
Send broadcast messages and read the account's monthly quota, via a channel access token.- Notes
- The owner pastes a long-lived channel access token from the LINE Developers console, not a password. Every post is a broadcast to all followers; individual followers cannot be targeted.
Blogs
WordPress
Coming soon- API
- WordPress REST API v2, via a WordPress.com OAuth2 app or a self-hosted site's Application Password
- What we publish
- Posts with a title, HTML body, categories, tags and a featured image, published, drafted, pending or private.
- Accounts
- Self-hosted WordPress sites (5.6+) and WordPress.com/Jetpack sites, one site per connection.
- Permissions requested
Create and edit posts and upload media on the connected site.- Notes
- Self-hosted sites connect with a WordPress Application Password that the site owner creates under Users > Profile > Application Passwords and can revoke on its own — never the account password. WordPress.com sites connect through WordPress.com's own OAuth login instead.
Ghost
Coming soon- API
- Ghost Admin API
- What we publish
- Posts with a title, HTML body, feature image, tags and visibility, published or drafted.
- Accounts
- Ghost 5.x sites whose owner connects them.
- Permissions requested
Create and edit posts and upload media on the connected site, via an Admin API key.- Notes
- The site owner creates a custom integration (Settings > Integrations > Add custom integration) and pastes its Admin API key; Lemmek signs a short-lived token for every call rather than storing a session or password.
Tumblr
Coming soon- API
- Tumblr API v2 (OAuth 2.0)
- What we publish
- Posts with text, up to 10 images or one video, and a link, published, drafted, queued or set to private.
- Accounts
- Tumblr blogs the user picks after signing in; access tokens are refreshed automatically.
- Permissions requested
basic, write, offline_access
DEV
Coming soon- API
- Forem API, used by dev.to and other Forem communities
- What we publish
- Articles with a title, Markdown body, up to 4 tags and a canonical URL, published or drafted.
- Accounts
- dev.to and other Forem-based community accounts that the user names.
- Permissions requested
Create and edit articles on the connected account, via an API key.- Notes
- The user pastes an API key from Settings > Extensions > DEV Community API Keys, not a password. Forem has no media upload API, so images must already be hosted elsewhere and are linked by URL.
Hashnode
Coming soon- API
- Hashnode GraphQL API
- What we publish
- Articles with a title, Markdown body, tags and a cover image URL, published to one of the user's publications.
- Accounts
- Hashnode accounts and the publications (blogs) they own.
- Permissions requested
Create posts on the connected account's publications, via a Personal Access Token.- Notes
- The user pastes a Personal Access Token from Account settings > Developer, not a password. Hashnode has no media upload API, so images must already be hosted elsewhere and are linked by URL.
Blogger
Coming soon- API
- Blogger API v3, via the same Google OAuth login used for YouTube
- What we publish
- Posts with a title, HTML body and labels, live or as a draft.
- Accounts
- Blogger blogs where the connected Google account is an admin or author.
- Permissions requested
https://www.googleapis.com/auth/blogger- Notes
- Blogger has no media upload API, so images must already be hosted elsewhere and are linked by URL in the post body.
Permission names reflect each platform's current documentation and may change as platforms update their APIs. We always request the smallest set of permissions required to publish. Users can revoke access at any time; see Data deletion.