# Reel API Effects Preservation Review

Keep requested native Reel effects separate from fields supported by the API route.

## Scope
Preparation and review only. No account action or professional decision.

## Inputs
Instagram Reel ID,requested music/stickers/text/polls/links,rendered file and intended route.

## Workflow
1. List which requested effects are already present in supplied rendered bytes.
2. Record documented API route cannot add listed music/audio,text/sticker,poll/link/hashtag effects.
3. Do not assume upload will recreate missing native edits.
4. Return content gaps without editing or publishing.

## Output contract
reel | requested_effect | rendered_evidence | API_add_support | manual_review | hold

## Fictional acceptance test
Fictional brief requests a poll and music, but supplied rendered file has neither. API upload is not proof those edits will be added. Rights and platform review remain separate.

## Review gates
Keep original values, source IDs and version dates. Unknown facts stay held. Use qualified review for hiring, legal and accounting conclusions. No send, share, sign-in, scheduling, ledger change or payment. Fictional contract review is not a live account compatibility test.

## Method source
https://help.planable.io/hc/en-us/articles/21715457579932-Scheduling-Video-Posts-Across-Multiple-Platforms-in-Planable

Checked October 15, 2026. Oct15 live AIS Search Console: marketing Copilot37 impressions, Planable/Claude45, Planable/ChatGPT24, campaignbrief12, investoragent19, MuseIndia115, cashflowforecasting13. Social calendar/reporting topics follow parent-query leads; other professions follow documented workflow needs, not measured exact intent. Site impressions are not monthly volumes; exact topic volume is unmeasured.