Start with the supported API contract
An agent framework needs an HTTP client, a secret store and a project mapping. Use the live OpenAPI definition to confirm supported fields. Do not assume that a package named in an older tutorial is installed, published or compatible with your framework version.
Prove authentication with a read request
Set REELING_API_KEY in your runtime secret store, then fetch projects. Use the selected project ID when requesting channels. This read request checks access without sending content to a social network.
curl --fail-with-body https://api.reeling.app/api/v1/projects \
-H "X-API-Key: $REELING_API_KEY"Separate drafting from publication
Have the agent prepare a proposal containing a video URL, caption, destinations and scheduled time. Review the proposal before POST /api/v1/publish. Store the returned post ID in the job record, and poll GET /api/v1/posts/{id} to inspect each destination.
Handle permissions and failures explicitly
TikTok inbox delivery requires finishing the post in TikTok. Public Direct Post availability depends on the app audit and account settings. A partial failure should update the job with the failed destination; do not automatically repeat every platform. Keep credentials and media URLs out of public logs.