Before you build
Use this handoff only after the creative is approved.
Arcads solves the upstream creative step. TokPortal publishes configured video slots through its own bundle workflow. The integration boundary should be an approved asset record—not a folder that automatically distributes every new render.
- Client-controlled Arcads and TokPortal accounts
- An approved, downloadable video asset and its internal identifier
- TokPortal API access, sufficient credits, and an authorized target country
- Approved caption, platform, publish window, and usage rights
- A named operator for the final publish decision and exceptions
TokPortal's official quickstart documents API-key authentication, current cost checks, idempotent bundle creation, presigned uploads, video-slot configuration, publishing, and status tracking. Confirm live parameters in the TokPortal quickstart and API reference.
Reference architecture
Seven stages from approved asset to tracked distribution
Define the approved asset contract
Start only after the Arcads output has an owner-approved asset URL, campaign name, target country, caption, publish window, and usage-rights confirmation. Missing approval stops the run.
Create a durable handoff record
Store the Arcads asset identifier, campaign metadata, approval timestamp, and a deterministic idempotency key before calling TokPortal. This record becomes the audit trail and duplicate guard.
Check the current TokPortal cost
Read the workspace-effective credit cost immediately before bundle creation. Do not hard-code a credit estimate or create a bundle when the approved ceiling would be exceeded.
Create one bounded bundle
Create the agreed platform, country, bundle type, and number of video slots with a unique idempotency key. Save the returned bundle ID beside the Arcads asset record.
Upload and configure the video
Request a presigned upload URL, upload the approved file, and configure its slot with the caption and target publish date. Never log an API key or temporary signed URL.
Require the final publish gate
Show the operator the bundle, account, country, slot count, and expected credit use. Publish only after the final approval state is present.
Track delivery and report exceptions
Poll the bundle state or consume approved webhooks, record the TokPortal request and bundle IDs, and surface failures or completed post links to the workflow owner.
Commercial and safety controls
Guard the two irreversible edges: credits and publishing.
Bundle creation and publishing must be separate states. Read the current credit cost first, create only the bounded bundle that was approved, configure the asset, and expose a final review record before publish.
Use an idempotency key on every supported mutation. A retry should return or reconcile the existing bundle—not create another credit-consuming run.
Definition of done
Acceptance tests for a fixed-scope pilot
- An unapproved or incomplete Arcads asset creates no TokPortal bundle.
- The run reads current workspace-effective credit costs before creation.
- Replaying the same handoff creates no duplicate bundle.
- The asset uploads and maps to the intended video slot.
- A credit, upload, or validation failure publishes nothing.
- The operator can review platform, country, caption, date, and expected credits before publish.
- A successful publish records the bundle and request identifiers.
- Status and exceptions reach the named workflow owner without exposing credentials.
Common questions
Arcads–TokPortal automation FAQ
Does this create videos in Arcads?
No. This blueprint begins with an approved Arcads output and automates the controlled handoff into TokPortal. Arcads generation can be scoped as a separate upstream step.
Who pays for Arcads and TokPortal usage?
The client owns both accounts and pays each platform directly. FlowPatch does not resell generation credits, TokPortal credits, accounts, or distribution.
Can the pilot publish automatically?
Only when the accepted scope defines a final approval signal, country, platform, slot count, credit ceiling, and rollback or pause owner. The safer default keeps publish behind an operator gate.
Does FlowPatch rent or operate social accounts?
No. TokPortal provides its own account and distribution services. FlowPatch implements the agreed API handoff and operational controls.
Is FlowPatch affiliated with Arcads or TokPortal?
No. FlowPatch is an independent integration service and is not affiliated with or endorsed by either platform.