Skip to content

Draft changelog: Batch Compliance byte-path cutover #435

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mintlify wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Draft changelog: Batch Compliance byte-path cutover #435

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions changelog.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,19 @@ keywords: ["changelog", "API updates", "release notes", "what's new", "API chang

To subscribe to updates, please [**“Turn on notifications”**](https://help.x.com/en/managing-your-account/notifications-on-mobile-devices#:~:text=In%20the%20top%20menu,%20you,you%20would%20like%20to%20receive) for [**@API**](https://x.com/api). You can also follow this changelog in your feed reader via the [**RSS feed**](https://docs.x.com/changelog/rss.xml).

<Update label="Sep 17, 2026" description="X API v2">
### Batch Compliance moves to `api.x.com` signed byte-paths

The [Batch Compliance](/x-api/compliance/batch-compliance/introduction) upload and download URLs are now served directly from `api.x.com` as signed, single-purpose links, replacing the previous `storage.googleapis.com` flow.

- Upload the dataset with a **single `PUT`** (up to **1 GiB**) to `upload_url`; download NDJSON results from `download_url`. The signed token is the credential on those byte-paths.
- New expiry fields on the job object: `upload_expires_at` (~15 minutes) and `download_expires_at` (~7 days).
- New endpoint: [`DELETE /2/compliance/jobs/:id`](/x-api/compliance/cancel-compliance-job) cancels a job that is awaiting upload or still processing. Only one active job of each `type` is allowed; creating a second returns **409**.
- Result records now use a two-part contract: `action` (`delete`, `rehydrate`, or `scrub_geo` for Posts; `delete` for users) and `reason` (`deleted`, `protected`, `deactivated`, `suspended`, `tweet_edited`, `geo_scrubbed`). When multiple events apply to the same ID, the highest-impact `action` wins.

See the rewritten [Quickstart](/x-api/compliance/batch-compliance/quickstart) and [Integration guide](/x-api/compliance/batch-compliance/integrate) for the full lifecycle, error catalog, and best practices.
</Update>

<Update label="Sep 17, 2026" description="X Ads API">
### Conversion API Google Tag Manager server-side template

Expand Down