How do you get oembed data using a Tweet ID?

[axemass]

The statuses/oembed docs state that:

Returns a single Tweet, specified by either a Tweet web URL or the Tweet ID, in an oEmbed-compatible format.

But I couldn’t find any reference about how to supply the Tweet ID parameter to the endpoint. Here are a few variations that I tried but didn’t work:

https://publish.twitter.com/oembed?url=463440424141459456
https://publish.twitter.com/oembed?id=463440424141459456
https://publish.twitter.com/oembed?tweet=463440424141459456
https://publish.twitter.com/oembed?tweet_id=463440424141459456
https://publish.twitter.com/oembed?tweetid=463440424141459456

[andypiper]

I think this may be a documentation error, since the docs state that URL is required, but do not provide an option for an ID on its own. The example on the page shows the URL parameter being used with the full link to a Tweet:

GET https://publish.twitter.com/oembed?url=https%3A%2F%2Ftwitter.com%2FInterior%2Fstatus%2F507185938620219395

There is a workaround, if you only have the Tweet ID. Here’s an example:

twurl -H publish.twitter.com "/oembed?url=https://twitter.com/twitter/status/1008419070524448768"

In this case, Tweet ID 1008419070524448768 actually belongs to my account. The returned oEmbed resolves to point to my profile - it does not matter which user handle is included in the URL.

{
  "url": "https://twitter.com/andypiper/status/1008419070524448768",
  "author_name": "Andy Piper (pipes)",
  "author_url": "https://twitter.com/andypiper",
  "html": "<blockquote class=\"twitter-tweet\"><p lang=\"en\" dir=\"ltr\">Mmm. <a href=\"https://twitter.com/bigfinish?ref_src=twsrc%5Etfw\">@bigfinish</a> sales are gateway drugs to so much good stuff I haven’t yet heard (or read!).</p>&mdash; Andy Piper (pipes) (@andypiper) <a href=\"https://twitter.com/andypiper/status/1008419070524448768?ref_src=twsrc%5Etfw\">June 17, 2018</a></blockquote>\n<script async src=\"https://platform.twitter.com/widgets.js\" charset=\"utf-8\"></script>\n",
  "width": 550,
  "height": null,
  "type": "rich",
  "cache_age": "3153600000",
  "provider_name": "Twitter",
  "provider_url": "https://twitter.com",
  "version": "1.0"
}

[axemass]

Thank you for replying.

I think this may be a documentation error, since the docs state that URL is required, but do not provide an option for an ID on its own.

I think this used to work in the past - one could fetch tweets using just the ID. I found an older issue which confirms it. You can find it here - Id parameter no longer works with statuses/oembed

There is a workaround, if you only have the Tweet ID …
…
it does not matter which user handle is included in the URL.

From Embedded Tweet CMS best practices under section Request fallback markup using oEmbed, the second paragraph reads:

A Tweet ID is preferred over a Tweet’s web URL: components of the URL such as the associated account’s screen_name may change; the Tweet ID is unique to the cited content and will remain the same.

It makes me question the reliability of the workaround: how long will it continue to work? Although, I did find a comment on Stack Overflow stating that this “bug/workaround” has been like that since 2012 - source.

Since this is something that used to work in the past, and one of the guides provided by Twitter emphasizes upon how a tweet ID is better than the full URL, can you (the Twitter dev team) please bring it back?

[andypiper]

We will work to resolve the issues across our documentation. I’ve confirmed that the ID parameter is not a valid option at this time. Thanks for bringing this to our attention and apologies for the issue.

[andypiper]

[andypiper]

Confirmed again that there are no plans to return the ID option here - we will remedy the documentation to reflect the new state.