Facebook Nested Comment Replies API

Use the legacy comment identifier as comment_id and preserve the matching post_id and expansion_token when the discussion response supplies them. The parameter schema lists these inputs as optional, but it does not establish that an empty request can resolve a thread. Treat expansion_token as a sensitive opaque continuation value: obtain it for the intended thread and do not publish it in shared examples. This endpoint has not been sampled, so parent-child fields, reply completeness and the precise input combination must be validated. Do not substitute a newer opaque comment identifier for the documented legacy ID.

API Features

Legacy thread identifier comment_id refers to the documented legacy Facebook comment ID rather than an arbitrary displayed key.

Thread expansion context Keep the matching expansion_token with the selected thread instead of inventing or reusing unrelated values.

Sensitive continuation handling No expansion-token default is published; supply an authorized value only when deliberately requesting expansion.

Reply-structure validation Preserve parent-child relationships only when the actual reply response exposes them.

Live API Demo

GET /api/project/facebook-scraper/comments-nested

API Response (JSON)

{}

curl -X GET 'https://api.opendata-api.com/api/project/facebook-scraper/comments-nested?key=<API_KEY>'

curl -X GET 'https://api.opendata-api.com/api/project/facebook-scraper/comments-nested?key=<API_KEY>'

📢

Need Help?

If you encounter API issues or need other API requirements, please contact us.

Use Cases

Let an analyst expand one relevant public comment thread on demand for context.
Evaluate legacy comment IDs from a discussion response before enabling nested-reply traversal.
Keep thread expansion values out of source-controlled examples and shared screenshots.
Reconstruct a sampled conversation only from validated parent-child fields rather than inferred reply order.

Frequently asked questions

Which kind of comment_id is required for nested replies?

Use the legacy comment ID for that thread, not a newer opaque key as a direct substitute. The matching input combination still needs small-scope validation.

Can I reuse expansion_token from another post?

Do not assume that you can. Use only a returned value that you are authorized to use and that belongs to the intended thread. Avoid exposing it in URL logs, screenshots or static examples.

Can an empty request return replies because all fields are optional?

There is no such guarantee. The field contract is not a working workflow; in practice, comment and expansion context that can locate the thread is needed.

Related operations

Guides

View Subscription Plans →

Expand Nested Comment Replies