Social publishing API requirements
A shared publishing API simplifies requests, but each destination still controls authorization, visibility, media acceptance and delivery. Check the actual channel capabilities before submitting.
Reviewed 2026-10-20 · Reeling product team
Compare the destination workflows
This is a workflow comparison, reviewed October 20, 2026. It combines Reeling’s maintained integration reference with the provider documentation linked below. It is not a live upload test or an account approval claim. Provider access can change; inspect the connected account before use.
| Destination | Reeling workflow | Check before publishing |
|---|---|---|
| YouTube | Video upload with explicit privacy and audience settings. | Connected channel, app/account capability, title, privacy and made-for-kids setting. |
| TikTok | Inbox delivery; direct mode depends on current app and creator capabilities. | Creator options, visibility eligibility and whether finishing in TikTok is required. |
| Reel through an authorized Business or Creator connection. | Professional account, relevant permissions, current app/tester access and media readiness. |
Choose visibility instead of relying on defaults
For a first YouTube integration check, select private visibility explicitly. The API supports privacyStatus and audience-related fields; inspect the intended channel and verify the actual destination after upload. A private test is different from a public Short.
TikTok requires approved scope and user authorization for Direct Post. Its documentation restricts unaudited clients and requires an audit to lift visibility restrictions. Reeling’s inbox flow requires finishing the post in TikTok. Never describe an inbox receipt as a public post.
Prepare the actual media file
Reeling’s overall v1 ingestion cap is 100 MiB. Individual destinations can impose smaller limits, duration rules or codec constraints. Review the returned capabilities and inspect the final export rather than trusting its filename.
Plan the frame, captions and file size before you send. These local tools make useful estimates, but they do not transcode, upload or validate a file against a destination API.
Use one channel for the first integration
The account may contain several channels for the same platform. Select project_id and channel_ids deliberately and run one reviewed destination before expanding to a mixed request. This makes failures and permissions easier to investigate.
If one platform succeeds and another fails, preserve both outcomes. Correct only the failed destination after checking for an existing upload; do not blindly resubmit the entire multi-platform request.
Where direct provider APIs still matter
A unified API does not replace platform policy or application approval. For provider-specific behavior, use the primary documentation and your returned channel options. Reeling’s supported fields may cover only part of the provider’s complete API.
The maintained platform matrix in the main developer portal covers additional destinations, inbox coverage and metric availability. Choose a workflow based on its current requirements rather than the number of platform logos.
Try it with your own workflow
Start with the offline examples, check the intended account and choose the next action deliberately.
Open the runnable examplesCreate a Reeling workspace