Skip to content
SUNGAI / DEVELOPER GUIDE

Your next integration starts here.

Explore a consistent workflow for connected accounts, original media, drafts, review and scheduling.

The workspace is an interactive browser demo. It uses sample accounts and local data. Demo keys, analytics, inbox replies and publication results do not access real platforms. The separate server API is documented below for future integration.

01 / Explore in minutes

  1. Open the workspace. No registration or password is required.
  2. Connect a sample channel. Choose a platform and a display name. No OAuth or password is collected.
  3. Create a post. Select one or several accounts, add content and preview each channel.
  4. Save drafts, review each one, explicitly choose visibility and confirm. Immediate demo posts complete after a short simulated processing step.
  5. Open the calendar to see schedules. Moving an approved post clears consent and requires another review.

02 / Try the API workflow

The playground runs requests against the same local demo records as the workspace. Select a preset, inspect its JSON and run it. POST /posts creates a local draft that appears immediately in Posts.

GET /accounts
GET /posts
GET /capabilities
GET /demo/analytics

POST /posts
{
  "accountId": "ACCOUNT_ID_FROM_GET_ACCOUNTS",
  "content": "Something worth sharing.",
  "requestId": "a-unique-operation-id"
}

These are in-browser operations, not public HTTP endpoints. Reusing requestId with different content is rejected. A saved draft is not an approval.

Try a request

03 / Accounts & capabilities

Ten platform identities are available to explore the interface. Connections are sample records and can be removed without touching real social accounts. Analytics, comments and messaging use illustrative data.

CapabilityDemo experience
PublishingCreate once. Preview every channel. Keep control of what goes live.
SchedulingPlan a week or a month ahead with a visual content calendar.
AnalyticsUnderstand reach, engagement and what your audience responds to.
CommentsRead, organize and reply to conversations in one inbox.
MessagingKeep your conversations together. Never lose the context.

TikTok video and Bluesky text adapters exist in the separate server implementation. TikTok still requires developer credentials and approval; the remaining platforms are interface demonstrations. No production analytics, comments or messaging adapters are connected.

04 / Your original media

Upload MP4, MOV or WebM videos, 1–180 seconds and up to 100 MiB per file. Originals are kept in browser IndexedDB and can be previewed after refreshing the page. The library allows 1 GiB. Cancel active drafts that use a file before deleting it. Uploaded media is not sent to our server.

05 / Review before delivery

Selecting multiple channels creates independent drafts. Each draft needs explicit visibility and creator confirmation. The TikTok demo offers SELF_ONLY visibility. Editing content or its schedule clears approval and invalidates an older review version.

draft → processing → published (simulated)
     ↘ scheduled ↗

Edit draft / reschedule → draft → review again
Cancel draft / scheduled → cancelled

“Published” in this workspace only means the simulation completed. It is never a platform receipt.

06 / Keep your calendar moving

Choose a future date and time in the composer or review editor. The calendar uses your device’s local time. Drag editable content onto a future day to move it to 10:00 and review again. Simulation advances while the page is open or when reopened; it does not run as a background server job.

07 / Explore keys & events

Create scoped demo keys, view their metadata and revoke them. They start with sg_demo_ and cannot authenticate real requests. Add an HTTPS webhook URL to explore sample delivery history. Tests create simulated events with a sample HTTP result; no request or retry is sent to the URL.

08 / Separate server API

The repository retains a Koa REST implementation with real authentication, scoped keys, private media, creator review, durable schedules and signed webhook delivery. It currently uses encrypted single-instance file storage. This demo frontend is isolated from it; using real accounts requires a production frontend connection and deployment work.

GET    /v1/capabilities       # public runtime configuration
GET    /v1/openapi.json       # full server API contract
GET    /v1/accounts           # real server authentication required
POST   /v1/posts              # create a server draft
POST   /v1/posts/:id/approve   # authenticated creator consent
POST   /v1/posts/:id/status    # actual provider status

TikTok requires official OAuth, appropriate permissions, a verified HTTPS domain and applicable Content Posting API approval. No code or demo substitutes for that approval. Bluesky uses a dedicated app password. Do not put provider credentials in this demo workspace.

Read the server OpenAPI contract ↗

09 / Limits & storage

Per browser: 10 active sample accounts, 10 active demo keys, 5 webhooks, 1 GiB of media, and the latest 100 operation records. Save important originals elsewhere. Export JSON or reset everything in Settings. There is no paid checkout and selecting a preview plan only saves a local preference.

Open workspace settings →