# API di Twitter – La mia app API Discourse per le anteprime dei tweet è stata sospesa **URL:** https://meta.discourse.org/t/twitter-api-my-discourse-api-app-for-tweet-previews-was-suspended/261777 **Category:** Support **Created:** [15 Aprile 2023, 8:38am UTC](https://meta.discourse.org/t/twitter-api-my-discourse-api-app-for-tweet-previews-was-suspended/261777 "2023-04-15T08:38:29Z") **Posts on this page:** 1 **Showing post:** 2
### Author: ![Jonathan5](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jonathan5/32/197134_2.png) [@Jonathan5](https://meta.discourse.org/u/Jonathan5) #### Post date: [15 Aprile 2023, 8:59am UTC](https://meta.discourse.org/t/twitter-api-my-discourse-api-app-for-tweet-previews-was-suspended/261777/2 "2023-04-15T08:59:44Z")
Penso che l’idea sia di far pagare le persone per accedere ai dati di Twitter tramite l’API, ma sembra che l’API oEmbed consenta l’incorporamento (utilizzando l’URL di un tweet esistente) senza costi: > [@Bye bye embedded tweet previews](https://meta.discourse.org/t/bye-bye-embedded-tweet-previews/261708/12?u=jonathan5): > > Where does this fit into the grand scheme of things? The oEmbed API returns simple embed HTML in an [oEmbed](http://oembed.com/)-compatible format. You can use the oEmbed API to programmatically return embedded content, such as [Tweets](https://developer-staging.twitter.com/en/docs/twitter-for-websites/embedded-tweets/overview) and [timelines](https://developer-staging.twitter.com/en/docs/twitter-for-websites/timelines/overview). The response from the oEmbed API will return an HTML snippet that will be automatically recognized when [Twitter’s widget JavaScript is included on the page](https://developer.twitter.com/web/javascript/loading). Please note that the API is recommended for performing tasks in bulk, and we advise using our robust [publish.tw…](https://publish.twitter.com/#) --- _[View the full topic](https://meta.discourse.org/t/twitter-api-my-discourse-api-app-for-tweet-previews-was-suspended/261777)._