Upcoming Changes
Upcoming breaking changes planned for the Ads API. Under normal circumstances breaking changes will be announced with at least 30 days notice. See also our recent changes.
Announced changes
Completed changes
| Announced | Effective Date | Change |
|---|---|---|
| 2015-02-24 | 2015-04-22 | Analytics Cost Rate Limiting |
| 2015-03-11 | 2015-04-14 | Targeting Criteria PUT Response |
| 2015-02-24 | 2015-03-31 | Null Values in Stats Time Series |
| 2014-12-24 | 2015-03-02 | Card Image Uploads |
| 2015-06-03 | 2015-07-01 | Deprecation of Card Analytics |
| 2015-04-21 | 2015-10-09 | Placements and Product Types on Line Items and Reach Estimate |
Ads API Versioning
| Announced | Phase | Effective Date | Status |
|---|---|---|---|
| 2016-03-01 | v1 preview | 2016-03-15 | On Schedule |
| 2016-03-01 | v1 generally available | 2016-03-31 | On Schedule |
| 2016-03-01 | v0 no longer supported | 2016-06-30 | On Schedule |
As per our recent announcement, versioning is coming to Twitter’s Ads API.
For more details on what Ads API v1 entails, have a look at our Ads API Version 1.0 overview page.
Changes to Rate Limit Windows
| Announced | Phase | Effective Date | Status |
|---|---|---|---|
| 2015-10-13 | 1 | 2015-11-11 | On Schedule |
| 2015-10-13 | 2 | 2016-01-06 | On Schedule |
In an effort to simplify how developers handle rate limiting in the Twitter Ads API, all endpoints on the API will soon be limited using 1-minute rate limit windows rather than 15-minutes. This moves all our endpoints to use the same duration as we already use for our analytics and write limiting schemes. It also results in shorter wait time between when a query is rate limited and when it may be retried.
As part of this change, developers may now access a single rate limiting doc to understand what their rate limits will be on the Ads API. Our rate limiting will be based on the developer’s access level.
We will be rolling these changes out in 2 phases. Phase 1 will include all developer applications in either the Developer or Basic tiers of access and will be effective Wednesday, November 11th. Phase 2 will include all developer applications in the Standard tier of access and will be effective Wednesday, January 6th.
Scoped Timeline Single User
| Announced | Effective Date | Status |
|---|---|---|
| 2015-11-20 | 2016-03-01 | On Schedule |
The user_ids parameter on the GET accounts/:account_id/scoped_timeline endpoint has been deprecated and replaced with the user_id parameter. As a result of this change, only a single user’s scoped timeline can be requested in a single query to the API. The user_ids parameter will be supported on the v0 endpoint until Tuesday, March 1st.