Platforms
Platform integrations
PolyglotMedia connects to four platforms through their official APIs. In every case the permission requested is the narrowest one that allows a video to be published to an account the company owns.
TikTok
TikTok receives the medium-length cut of each recipe, in Portuguese, on the brand's own profile — one video per day.
APIs used
- Login Kit
- One-time authorisation of the brand account by the operator
- Content Posting API
- Uploading and publishing the finished video file
- Scopes requested
user.info.basic·video.publish- Upload method
FILE_UPLOAD— the file is sent directly from the operator's machine
What the authorisation flow looks like
- The operator starts the connectionFrom the panel's settings screen, on their own machine.
- TikTok's authorisation screen opensThe operator signs in to TikTok directly. PolyglotMedia never sees the password — it only receives the authorisation code TikTok returns.
- The refresh token is storedEncrypted, in the local database. Short-lived access tokens are generated from it at publish time and never written to disk.
- Publishing begins on scheduleAt the configured time, the video file is uploaded and submitted for publication.
Publishing and confirmation
An accepted upload is not the same as a published video: TikTok processes the file afterwards and may still reject it. PolyglotMedia therefore polls the publication status until TikTok reports a final outcome, and records that outcome against the video. Without this step a rejected video would be marked as successfully posted.
Large files are sent in chunks, as the API requires, and the application computes the chunk plan from the file size rather than assuming a single-part upload. Recipe videos routinely exceed the single-chunk limit.
Deliberate limits
- Only one profile is ever connected — the brand's own.
- Only content produced by the company is uploaded. Nothing is reposted from other creators.
- Publication frequency is one video per day, on a fixed schedule.
- No TikTok content, metrics or user data is read back into the application.
Facebook is where the multi-language operation actually lives: six pages, one per language, each receiving the long and short cuts in its own language.
The application publishes with page access tokens issued for pages the company administers. Tokens are validated when a channel is saved, so an expired or misapplied credential is caught at configuration time rather than silently failing at 6pm.
- Content published
- Long videos and short videos, six languages
- Credential type
- Page access token for a page owned by the company
- Data read
- Page name and page identifier, to confirm the correct destination
Instagram receives the short cut in Portuguese, published as a Reel to the brand's business profile. The integration relies on the same application and the same page credential as the linked Facebook page — Instagram business accounts are addressed through their connected page.
YouTube
YouTube receives the long cut in Portuguese on the brand's channel. The upload scope is the only permission requested; the application does not read channel analytics, comments or subscriber information.
What is stored for each connection
Regardless of platform, a connected channel stores the same three things locally: the account identifier, the credential needed to publish, and the schedule the operator configured. The credential is encrypted at rest. Removing the channel from the panel deletes all three.