Public image and video URLs are checked before Meta fetches the carousel.
Threads
Meta OAuth 2.0
Arrange a Threads carousel and the replies that follow it.
This page is for people deciding whether OpenPost fits their Threads publishing workflow.
Schedule text, image, video, carousel, and reply-thread posts for connected Threads accounts.
Implemented: Publishing is implemented
Managed certification: No managed provider-format certification claim is current.
Formats and limits
Different formats, different rules.
OpenPost checks the text and media rules for the format you choose.
Post or reply thread
- Text
- 500 characters
- Media
- Text only
Image or video
- Text
- 500 characters
- Media
- One public HTTPS media item
Carousel
- Text
- 500 characters
- Media
- 2-20 public HTTPS images or videos
Provider limits and scope
- 500 characters
- One media item or a 2-20 item carousel
- Reply chains
- Public media URL and approved Meta app access required
Connect and test
Set up Threads in three checks.
- 1
Configure the Threads app credentials and exact OAuth redirect URI.
- 2
Make stored media reachable through a public HTTPS URL that Meta can fetch.
- 3
Connect the account and test image, video, or carousel publishing from production-like hosting.
Known limits
What can still block a post.
- Meta fetches media server-side; localhost, private URLs, and inaccessible object storage will fail.
- Video processing and account permissions can still fail after a successful OAuth connection.
- Local development needs a public tunnel for callbacks and media.
Account requirement: An approved Meta app and public HTTPS media hosting for media posts.
Verification: Verify that Meta can fetch the exact production media URL before scheduling media-heavy work.
Use the current callback address, permissions, and media setup.
Social network developer pages change. The OpenPost guide lists the settings and checks you need now.
Read the Threads guide