Add publishing to your product.

Walkthrough

1. 01

   Design the product confirmation before the API call

   Open this area in SosoAPI

   • In the SosoAPI app, select the intended Workspace and review its connected account. In your product mockup, show that same user-selected Workspace and account rather than choosing one silently.

   • Show the exact caption, account, local time, and timezone in a confirmation step. Require the person to choose Schedule; opening the form must not submit anything.

   What to expect

   A human can see the target and timing before the write. The fictional product mockup is a design exercise, not an installed customer integration.

2. 02

   Read the current Scheduled Posts from your server

   • Replace <workspace-uuid> with your selected Workspace ID, then run this read-only request on your server:

   • const apiKey = process.env.SOSOAPI_API_KEY;
     if (!apiKey) throw new Error("Configure a SosoAPI API key on your server");
     const response = await fetch(
       "https://gqeshlawtcexsapabaui.supabase.co/functions/v1/studio-api/scheduled-posts/list",
       {
         method: "POST",
         headers: {
           "Authorization": "Bearer " + apiKey,
           "Content-Type": "application/json"
         },
         body: JSON.stringify({"workspace_id":"<workspace-uuid>"})
       }
     );
     const result = await response.json();
     if (!response.ok) throw new Error("SosoAPI request failed: " + response.status);
     // Use result in your server response; never return or log the API key.

   • Use the returned data to refresh your product’s list. Keep the user’s confirmation separate from this read.

   What to expect

   You receive the Workspace’s current posts or an authorization/validation error. This read-only request creates no posts.

3. 03

   Submit only after explicit user confirmation

   • Open Calendar and choose New Post to compare the review step with the same action in the App.

   • Replace every placeholder with your authorized IDs, a future ISO timestamp with offset, and a unique idempotency key. Review the account, copy and time before running this server-side request.

   • const apiKey = process.env.SOSOAPI_API_KEY;
     if (!apiKey) throw new Error("Configure a SosoAPI API key on your server");
     const response = await fetch(
       "https://gqeshlawtcexsapabaui.supabase.co/functions/v1/studio-api/scheduled-posts/create",
       {
         method: "POST",
         headers: {
           "Authorization": "Bearer " + apiKey,
           "Content-Type": "application/json"
         },
         body: JSON.stringify({
       "workspace_id": "<workspace-uuid>",
       "social_account_id": "<threads-social-account-uuid>",
       "caption": "A small note for later: Harborlight Journal is making room for shorter daily reflections. Keep one thought; leave the rest for tomorrow.",
       "hashtags": [],
       "media": [],
       "provider_payload": {"platform": "threads", "publish_options": {"post_type": "TEXT"}},
       "scheduled_at": "<future ISO-8601 instant with offset>",
       "display_timezone": "Asia/Hong_Kong",
       "idempotency_key": "<unique-stable-key-for-this-intent>"
     })
       }
     );
     const result = await response.json();
     if (!response.ok) throw new Error("SosoAPI request failed: " + response.status);
     // Use result in your server response; never return or log the API key.

   • Running this request creates a real schedule. Submit only after the user confirms, and never expose the API key to a browser.

   What to expect

   A valid accepted response identifies the resulting Scheduled Post; it is not proof that a provider has published it. A denied capability, invalid scope/account, unsupported payload, or rejected schedule must be shown as an error, not reported as success.

4. 04

   Render the returned state and give the user a safe follow-up

   Open this area in SosoAPI

   • Store the returned Scheduled Post ID and display its current state, destination, and schedule in the product.

   • Link the user to the matching Scheduled Post detail. If delivery needs a person, link the Needs Attention item instead of silently resubmitting.

   • Do not label the request published until the final provider-confirmed status is recorded.

   What to expect

   The product distinguishes a request receipt from scheduled, publishing, published, failed, and unknown observations. Unknown results are reconciled against the existing post before a new write.