Sebagian Tidak Bisa Diaksesshare-external
Error when publishing a single-thread post with video through Threads API
3

I am trying to post a video through the Threads API in a single-thread post.

I upload the video to a public URL, using Vercel Blob, and I have verified that the video is there.

I use the POST /{threads-user-id}/threads endpoint to create a media container successfully.

When I use the POST /{threads-user-id}/threads_publish endpoint to publish the container, I get an error, stating: "The media with id {container-id} cannot be found."

The Threads API Troubleshooting page says: "If you are able to create a container for a video but the POST /{threads-user-id}/threads_publish endpoint does not return the published media ID, then you can get the container's publishing status by querying the GET /{threads-container-id} endpoint. ... We recommend querying a container's status once per minute, for no more than 5 minutes."

So I waited for 60 seconds and then queried the GET /{threads-container-id} endpoint, but it returns the following error:

{
  status: 'ERROR',
  error_message: 'UNKNOWN',
  id: '{threads-container-id}'
}

The same code successfully publishes a single-thread post with an image (using the image_url parameter instead of video_url, of course).

I have also verified that the video conforms to Threads' Video Specifications (screenshot attached).

Any suggestions are welcome.

Thanks, Michael

Michael
Ditanyakan sekitar 5 bulan yang lalu
Michael

In case this is helpful for debugging, the video is here:

https://fku5s5wau2ccuoic.public.blob.vercel-storage.com/SampleVideo_1280x720_1mb-oGIYmQAizGohakMaHorTkdCRVDlfFE.mp4

The container ID is: 17943515876730115

The fbtrace_id from the error returned by the POST /{threads-user-id}/threads_publish endpoint is: AG2eghOPVxr2j4Lu43oWMD9

29 Juni pukul 16.23
Paul

I’m also facing the same issue. There’s no specific error returned when supplying the video_url. The media container creates and returns an id. The troubleshootingu steps gives no specific error why, just returns UNKNOWN.

13 Juli pukul 18.59
Riddhi

facing the same issue, the documentation does not provide any context regarding the unknows error

4 Agustus pukul 22.32