Read Public Post Reshare References

View all Facebook Public Data API endpoints →

Pass the share identifier supplied with post details in the public parameter named post_id; the documented prerequisite calls it share_id, while the sampled Page-post feed used shares_id. Preserve the exact field and value from the source response and validate compatibility for this route rather than assuming all post identifiers are equal. cursor is optional. No reshare response was sampled, so its field layout and coverage are unverified. Only visible reshares may be accessible; this does not expose private sharing or a complete dissemination network.

API Features

Share-key input handoff The parameter remains post_id, but the documented value comes from the post share reference.
Share-field naming caution Documentation mentions share_id and a sampled feed contains shares_id; compatibility is not assumed.
Visible dissemination scope The route does not promise access to private shares or all sharing activity.
Independent reshare cursor Treat reshare continuation separately from the parent posts and comments cursors.

Live API Demo

GET /api/project/facebook-scraper/reshares

Request cost is temporarily unavailable. No price is assumed.

View pricing

API Response (JSON)

{}
curl -X GET 'https://api.opendata-api.com/api/project/facebook-scraper/reshares?key=<API_KEY>'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

Frequently asked questions

What should I enter in post_id for the reshare endpoint?

The documented flow uses a share reference: the description calls it share_id, while the post sample contains shares_id. Preserve the source field and validate compatibility first.

Can I read private shares?

No such capability is promised. This endpoint targets visible reshare references and does not guarantee a complete dissemination network.

Can I reuse a comment cursor to continue reading reshares?

No. Use a cursor returned by the same reshare collection and manage continuation context separately for each content type.

Related operations

Guides

View Subscription Plans →