#Download twitter video from dm update
#Download twitter video from dm full

If the Line Item start_time and end_time is null, the values that will appear will be the same as the Campaign start_time and end_time.

If you have not yet upgraded to v11, you may begin to see start_time and end_time even if previously not set. This release is related to our plans to add utility to our Line Item capabilities in the future, ultimately giving advertisers more control over how they manage Line Items to meet the specific requirements of their Campaigns. This is because we moved these parameters from the Campaign level to the Line Item level.

Most relevant to: developers offering campaign management or ad buying servicesĪs of v11, the start_time and end_time parameters on the Campaigns endpoint have been deprecated.

Moving start & end times to Line Item level 13 months is the maximum allowable value for expires_at at this time. However, we will overwrite any expires_at timestamps greater than 13 months to equal 13 months. If you have not already, adopt a more regular updating cadence to prevent Audiences from expiring. This will require the expires_at parameter to either be not set or set with a timestamp that is less than 13 months from the request timestamp.Īs of v11, requests that include an expires_at timestamp beyond this 13 month timeframe will result in an error. There is a new validation rule based on a 13 month audience expiration date. This helps improve the quality of recommendations provided by the targeting_suggestions endpoint, which in turn can help improve the targeting options available for advertisers. The back-end system for returning USER_ID has been updated.

Most relevant to: developers offering campaign management, ad buying, or audience services.

What’s changing: Back-end improvements to targeting_suggestions for USER_ID

#Download twitter video from dm update

We previously shared a related update on these endpoints.

#Download twitter video from dm full

Full details in our documentation.Īs a reminder, the new JSON-based endpoints allow developers to build Cards using components rather than working with Card-specific resources. The PUT endpoint will allow advertisers to manage Card details such as Card name, URL, or media. This is an exciting update, as it enables Card editing for our new JSON-based Cards endpoint. The new Cards endpoints, PUT and DELETE, are now globally available.

Most relevant to: developers offering campaign management, ad buying, or creative services.

What’s new: Card PUT and DELETE endpoints Note: As of this release, Version 9 (v9) of the Ads API has reached its end of life and is no longer available. We encourage all developers to migrate to the latest version of the Ads API as soon as possible to avoid any service disruptions. On October 4, 2022, the existing version 10 (v10) of the Ads API will no longer be available. This release includes new Card editing functionality, Line Item updates, and continues to improve parity with Twitter Ads Manager.Īs with our previous versions, there will be a 6 month transition period to migrate to v10. Starting today, March 31, 2022, version 11 (v11) of the Twitter Ads API is available to all developers. This is because we moved these parameters from the campaign level to the line item level. We’ve corrected this post to reflect that this parameter exists at the Campaign level.Ĭorrection April 21: As of v11, the start_time and end_time parameters on the Campaigns endpoint have been deprecated as part of the Line Item changes. Correction May 25: The new budget_optimization parameter was previously listed as a Line Item endpoint.