#1

Hi!

When we provide parameters such as video_id, video_title, video_description, video_cta_value, video_cta to
POST accounts/:account_id/tweet endpoint, create the tweet and then call GET accounts/:account_id/tweet/preview/:tweet_id, none of this features provided seem to be visible in preview html. The preview looks the same as if only video_id would be provided to create tweet endpoint.

My question is; is this ok and these parameters have no effect on the tweet, or is the endpoint not returning the right html preview?

Also, GET accounts/:account_id/tweet/preview (so endpoint for seeing preview before tweet has been created), supports only video_id parameter but not the other video related params. Are you planing on adding them in the later versions of ads API?

Many thanks in advance,
Dejan

#2

@dejan

We recommend you using our Draft Tweets endpoints instead, for generating HTML previews.

See below post:

Some parameters such as “video_cta_value, video_cta” you mentioned are only required when you create an “actual” tweet, not for a draft tweet. For instance, you can create one of the video cards then get card_uri , so that you can create a draft tweet by specifying this card_uri.

#3

Thanks for the answer, but that’s not really the explanation we were looking for.

We already know about the benefits of draft tweets and previews from that endpoint, but the
“draft workflow” doesn’t suit our platforms tweet creation flow and so we don’t use them, and
also this question has nothing to do with cards, but only tweets with video.

Our question was, why video description and title is not returned in html response (preview)
from “GET accounts/:account_id/tweet/preview/:tweet_id” endpoint, while on the other hand
video cta and cta_value(url) is. We provided all this parameters while creating tweet on
“POST accounts/:account_id/tweet” endpoint.

Also, we know these parameters are not required when creating a new video tweet, we are just
wondering why are these options on create tweet endpoint, if we cannot see them on actual
promoted tweets with preview.

#4

@dejan,

My question is; is this ok and these parameters have no effect on the tweet, or is the endpoint not returning the right html preview?

The later one, that’s why our documentation says: "Note: Previews are approximate.", unfortunately.
As we mentioned the other day:

this endpoint is not perfect if you want to see an “actual” tweet preview. Please consider draft_tweets endpoint instead. Or, you can simply create a nullcasted tweet (nullcasted tweets do not appear in the public timeline and are not served to followers.) and then see a tweet link that shows actual tweet preview which is accessible from across the platforms as well (e.g., PC, iOS, Android …etc).

Out of curiosity, what is your exact use case for this accounts/:account_id/tweet/preview endpoint even though we introduced a better way for this in v3?

Best,
Shohei

#5

@jrsyo thanks for your answer and to answer your question:

We use tweet/preview endpoints so our clients can see how their promoted tweets look like when they’re creating them on our platform. As I mentioned earlier we are aware of the benefits of draft tweets, but other than using them for tweet previews, we don’t see any other added value in them. It would also take us some time to rewrite our current code so in would include draft tweet creation step, so for now we shall stick to tweet/preview endpoints until possible.

Best,
Dejan

#6

To add to what @jrsyo has already said, this is just a display issue on the preview. When you use the video title, description, etc. when creating Tweets, that information is applied to the Tweet you create. It’s just not reflected on the preview itself.

#7

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.