Announcement: update to scheduled Tweets

announcements

#1

Today we’re announcing several updates to our Scheduled Tweets endpoints.

  • It’s now possible to update whether specific Scheduled Tweets are served to followers or not. We refer to the former case as organic and to the latter as nullcasted. To enable this, we’ve added the nullcast parameter to the PUT accounts/:account_id/scheduled_tweets/:scheduled_tweet_id endpoint.
    • As a reminder, organic Tweets (nullcast=false) can only be created for the authenticated user. This means it will not be possible to update a Scheduled Tweet to organic when the ad account’s FULL promotable user is different from the authenticated user.
  • We’ve added the ability to unset (remove) media from Scheduled Tweets. To do this, use the PUT accounts/:account_id/scheduled_tweets/:scheduled_tweet_id endpoint and specify the media_ids parameter without a value (media_ids=).

Note: Any updates to Scheduled Tweets must be made before the scheduled_at time.

In addition to these changes, we’ve added the media_keys response attribute, an array, to all Scheduled Tweets responses.

  • A media key begins with an int, is followed by an underscore, and ends with a long value (the media ID). As an example, see: 3_917438348871983104.

We’re continuing to work to make our endpoints more useful and welcome your feedback. In fact, the first change listed in this announcement was prompted by this forum post.

The documentation will be updated shortly.

Twitter Ads API Team


Ads API Version 2
Ads API Version 3
Not able to change the scheduled tweet type(organic <->promoted)
#2

#3

#4

It’s now possible to unset (remove) cards from Scheduled Tweets. Using the PUT accounts/:account_id/scheduled_tweets/:scheduled_tweet_id endpoint, specify the card_uri parameter without a value. See example below.

The Scheduled Tweet to remove the card from:

$ twurl -H ads-api.twitter.com "/2/accounts/18ce54d4x5t/scheduled_tweets/918876176055017473"
{
  "request": {
    "params": {
      "scheduled_tweet_id": 918876176055017473
    }
  },
  "data": {
    "completed_at": null,
    "id_str": "918876176055017473",
    "text": "to unset card_uri",
    "user_id": "756201191646691328",
    "scheduled_status": "SCHEDULED",
    "id": 918876176055017473,
    "media_ids": [],
    "nullcast": true,
    "created_at": "2017-10-13T16:28:46Z",
    "scheduled_at": "2018-01-01T00:00:00Z",
    "card_uri": "card://867177663303000065",
    "updated_at": "2017-10-13T16:28:46Z",
    "tweet_id": null,
    "media_keys": []
  }
}

Unsetting the card:

$ twurl -X PUT -H ads-api.twitter.com "/2/accounts/18ce54d4x5t/scheduled_tweets/918876176055017473?card_uri="
{
  "request": {
    "params": {
      "scheduled_tweet_id": 918876176055017473,
      "card_uri": ""
    }
  },
  "data": {
    "completed_at": null,
    "id_str": "918876176055017473",
    "text": "to unset card_uri",
    "user_id": "756201191646691328",
    "scheduled_status": "SCHEDULED",
    "id": 918876176055017473,
    "media_ids": [],
    "nullcast": true,
    "created_at": "2017-10-13T16:28:46Z",
    "scheduled_at": "2018-01-01T00:00:00Z",
    "card_uri": null,
    "updated_at": "2017-10-13T16:29:25Z",
    "tweet_id": null,
    "media_keys": []
  }
}

#5

We have published a Scheduled Tweets guide with details on how to create, edit, manage, and generate HTML previews for Scheduled Tweets as well as how to promote them in campaigns. The guide also explains what happens when a Scheduled Tweet goes live.