Choose an integration your client supports
Different assistant products support different tool transports and authentication methods. Check your client version before importing a schema or assuming it can send custom headers. The stable Reeling contract is its HTTPS REST API; MCP is another option for compatible clients.
Configure read operations first
Map GET /api/v1/projects and GET /api/v1/channels?projectId=YOUR_PROJECT_ID. Store the Reeling key in the connector secret store and send it in X-API-Key. Return only the project and channel information needed for the task; never include credentials in tool output.
Treat publishing as an explicit action
Map POST /api/v1/publish only after read access works. Require the user to review the project, destination accounts, caption, media and timing. The API uses scheduled_for for scheduling. Do not promise that one natural-language request will automatically produce a compliant video and publish it everywhere.
Return the real outcome
Save the post ID, check GET /api/v1/posts/{id}, and report the destination statuses. Distinguish queued, scheduled, partially published, failed and inbox delivery. A connection to Reeling does not remove a platform’s account, consent or approval requirements.