Which product-launch Reel questions have answers, and how do I check their replies?
To find which questions under a product-launch Reel already have answers, fetch the Reel’s top-level comments with instagram.fetch_post_comments_v2, passing the Reel’s numeric media pk as media_id, and export the comments to comments.csv. Shortlist the questions about accessories, cleaning or cup types. For each shortlisted question, fetch the replies with instagram.fetch_comment_replies, using the question’s comment ID as the parent. Then mark each question as answered, needs_context or no_answer_observed in this review.
For example, when a viewer asks “Can I use a short cup?”, keep the quote and the Reel link. When a reply mentions a height limit, pair the reply with the question and check the height limit against the product documentation.
Move one question toward an action
- Confirm the Reel. Reuse the media ID from the saved post details, as described in the post-to-comment handoff.
- Save the root comments. Review the chosen pages of
comments.csvand select the product-use questions, keeping each question’s original wording beside your summary. - Retrieve replies for selected questions. A reply preview under a root comment does not show the whole thread. When a question needs context, prepare a reply request for the question’s root comment and save the reply branch in its own folder.
- Check whether a reply answers the question. Read the question and the returned replies. Support each decision in
resolution.jsonwith an actual reply ID and a verbatim excerpt. - Hand off the follow-up work. For each question, state what needs checking and who should handle the check. Creating
resolution.jsondoes not reply to viewers or close any issue.
To hand the review to an assistant connected to BeatAPI, use a prompt like:
Review accessory and cleaning questions on this launch Reel. Preserve original wording and read selected reply threads when context is needed. Separate answers supported by replies, questions needing more context and questions with no answer observed in this collection, with next actions.
Read the deliverables
answered requires a saved reply whose text supports the answer. needs_context means the saved replies are not enough to decide. no_answer_observed describes only the saved sample. Check every answer against the product information before you use the answer.
Steps 1–7 below cover retrieval, export, replies and review. The Python scripts only process saved files; each save_call.sh run makes one data request. Reuse saved responses when available.
1. Start with the media ID and a page budget
Use the original numeric-string pk from the saved post detail that matches the Reel’s shortcode, not the URL shortcode and not the generic id column of the snapshot CSV. The URL-to-comments handoff reads data.data.pk for v2 or the matching data.items[].pk for v3 and builds the complete first-page request. Reuse the post detail saved in the post-snapshot guide instead of paying for another conversion. Record in your request log which Reel the media ID belongs to: the comment response does not identify the Reel on its own.
Request root comments with data:instagram.fetch_post_comments_v2; current rates are on the pricing page. Decide how many pages to buy, and count root-comment requests, selected-reply requests and optional detail requests separately. Row counts come from the actual responses; the local export makes no requests.
2. Save the first page and its request log
Write request-1.json with your verified numeric media ID in place of the sample ID:
Save the following script as save_call.sh, then run bash save_call.sh request-1.json root-call-1 once per page within your approved page budget. Each run sends one paid request and does not retry; curl -q ignores local curlrc retry and redirect settings. The output folder must not exist yet.
save_call.sh keeps the exact submitted request, the response headers and body, the local UTC request-start time and the HTTP status. save_call.sh writes entry.json only after HTTP 200, and instagram_comments.py still checks the response envelope. Copy each generated entry.json object into the pages.json array. The example below illustrates the expected pages.json format. If curl, the network or HTTP fails, stop and keep the folder; do not run save_call.sh into the same folder again. Never put authorization headers in the log.
3. Export saved pages and prepare the next request
Save the following script as instagram_comments.py. The script reads direct /v1/social-data/call JSON, not a trimmed MCP preview. A relative response_file path resolves against the folder of pages.json; save_call.sh already records an absolute path. The script checks that all pages share one media ID and one explicit sort order, that collection times carry a timezone and run in order, and that the cursor chain is unbroken. A response without data.comments stops the export instead of passing as an empty page. comments.csv keeps the first observation of each root comment; the raw pages keep later variants unchanged. Replies are never added to root comment counts.
4. Continue only within your budget
Run python3 instagram_comments.py pages.json review-1. If review-1/next-request.json exists, the file carries the previous page’s next_min_id as the next min_id, byte-for-byte as a string. Do not parse and rewrite next-request.json, do not change its escaping by hand, and do not reuse the file with another media ID or sort order. To buy the next page, run bash save_call.sh review-1/next-request.json root-call-2. Append root-call-2/entry.json as another object in the pages.json array, then export into a new folder such as review-2. Do not edit a saved request or rebuild a cursor by hand, and never append a page after a terminal page.
Stop when you reach your budget or when the export reports provider_end, an empty page with more=true, a repeated or missing cursor, a missing boolean more flag, or a gateway failure. For each stop condition, instagram_comments.py writes no next-request.json. A missing field is a schema discrepancy to report, not zero comments: keep the response and its request ID for support, and do not automatically try another paid endpoint. A successful empty comments: [] with more=false produces a header-only CSV and records the end state.
5. Deliver the evidence, not “all comments”
comments.csv has one row per observed root comment ID with the original text (escaped against spreadsheet formulas), likes, raw timestamps, reported reply count, preview object count, request ID and collection time. In Excel, import the media and comment IDs as text to avoid precision loss. Zero stays zero and missing values stay blank. Raw timestamps are not converted to an assumed timezone or unit. Usernames and profile images are left out of the sheet on purpose.
reply-previews.jsonl keeps the documented preview objects under the root comment they appeared under; the file adds no inner reply fields and does not represent a full thread. coverage.json records every page, the page hash, the reported total and the stop reason; raw-page-*.json holds the original bytes. All of these source files can contain personal data, so limit access and share a separately redacted copy. The provider’s reported total does not promise how many comments can be retrieved, and provider_end does not show that deleted, hidden or private comments were captured.
For launch feedback, label the rows of comments.csv by hand with decision, topic and an exact source quote. Exclude promotions and duplicates with a reason, and report the number of reviewed and unreviewed root comments and the number of Reels. Count complaints within the reviewed sample only; the count does not measure customers, purchases, prevalence or product defects. Check any quote that begins with a formula character against the raw JSON, not the escaped CSV cell. Read the reply coverage answer before promising anything about replies.
Evidence and scope
The Comments V2 response carries comment IDs, text, counts, timestamps and cursor fields under data. Check the data field paths in a saved response before exporting a new batch, and replace the placeholder IDs and timestamps in the examples with your verified request values.
6. Expand one selected root into a reply evidence sheet
When a root comment contains an unresolved product question, take the root comment’s comment_id from comments.csv. Keep the root export folder unchanged: instagram_replies.py checks the root page’s source hash, the request ID and the presence of the root comment before accepting reply pages. Preview objects are not merged into the reply count.
Request replies with data:instagram.fetch_comment_replies, passing the same media ID and the selected root comment’s pk as comment_id. Save each root comment’s replies as a separate branch, and estimate the cost of the pages you choose with the current pricing.
Save the first reply request as reply-request-1.json, with your selected media ID and root comment ID in place of the sample IDs. Run bash save_call.sh reply-request-1.json reply-call-1, then put reply-call-1/entry.json into the reply-pages.json array:
Replace the placeholder IDs and timestamps above with your actual request values. Save the following script as instagram_replies.py, then run python3 instagram_replies.py review-2 reply-pages.json replies-1, with your actual root export folder in place of review-2.
replies.csv keeps requested_root_id separate from each returned parent_comment_id, because a reply’s immediate parent is not always the requested root comment. Each row keeps the original reply ID, text, likes and raw timestamps. coverage.json records the root page’s source hash and the reply pages retrieved for the root comment. Keep both the root export folder and the reply folder for review.
Reply pagination continues with data.page_info.next_min_id. Although next_min_child_cursor may also appear in response metadata, instagram_replies.py does not substitute next_min_child_cursor because the two fields are not interchangeable. If more is true but data.page_info.next_min_id is missing, the script stops with missing_cursor; keep the response for investigation. Otherwise next-request.json holds the same media ID, root comment ID and cursor for the next paid request. As with root pages, append the actual request log and export into a new folder.
Review each question with the root comment text and replies.csv, and record a manual resolution of answered, needs_context or no_answer_observed with the supporting reply ID and an exact quote. provider_end describes pagination only; provider_end does not show that no hidden or deleted replies exist. No message is sent to commenters.
Identifier precision prerequisite
Unquoted JSON numbers above 9007199254740991 can lose precision when decoded as float64 before reaching the Python scripts. The scripts therefore reject unquoted numeric IDs above 9007199254740991, while IDs originally encoded as strings stay exact. Do not “fix” a rejected numeric ID by wrapping the rounded value in quotes: stop the export and keep the request ID for investigation. Python’s large integers and spreadsheet text formatting cannot restore precision already lost in a rounded number.
Check every observation before deduplication
Both exporters validate counts, timestamps and returned parent IDs before skipping a repeated ID, so a malformed later copy of a comment cannot disappear just because the same ID appeared on an earlier page. Valid changed values still follow the first-observation policy of the CSV; the raw pages keep every observation, so the CSV is not a latest-state merge. Counts accept zero, safe nonnegative integers and original ASCII digit strings; negative, abbreviated, boolean or unsafe numeric values stop the export. Missing counts stay blank. A success envelope that also carries an error is rejected.
7. Finish one question with an auditable manual resolution
replies.csv alone is not a product-support conclusion. For one selected root comment, read the root comment and its saved replies, then record a manual decision. Use answered only with a saved reply ID and an exact supporting passage. needs_context means the saved evidence is insufficient. no_answer_observed means you found no answer in the saved sample, not that nobody ever answered.
Save review.json with your actual root comment ID and reply ID. The example below illustrates the expected review.json format:
For no_answer_observed, omit reply_id and quote, and list the pages you reviewed in reviewer_note. For needs_context, attach a matching quote when one helps, or omit both evidence fields. resolve_question.py checks that the evidence links to a saved reply; the script does not judge whether the reply is correct or helpful.
Save the following script as resolve_question.py and run python3 resolve_question.py review-2 replies-1 review.json question-review, with your actual root and reply export folders. The output resolution.json contains the selected root comment, the manual judgment, the exact quote with its source, the observed reply count and the collection stop reason. review-input.json keeps the original manual input. The script makes no API request and sends no reply.
Keep the question-review folder private until the quoted content is reviewed for sharing. resolve_question.py checks the evidence quote against the raw response text, not the spreadsheet-escaped cell. Changed raw bytes, a wrong media ID or root comment, missing IDs, an invented quote or a mismatched coverage count stop the review. Local hashes show that the files are consistent; the hashes are not a server signature. An answered label is a human assessment, not a verified purchase, a resolved support ticket or a promise that all replies were collected. When you aggregate later, do not count unreviewed root comments as unanswered.

