---
title: "Making bulk changes to Changelog posts"
slug: "making-bulk-changes-to-changelog-posts"
updated: 2026-08-07T20:06:23Z
published: 2026-08-07T20:06:23Z
canonical: "help.userflow.com/making-bulk-changes-to-changelog-posts"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.userflow.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Making bulk changes to Changelog posts

The Changelog dashboard doesn't have bulk actions — each post is edited individually. If you need to change many posts at once, the API is the way to do it.

This comes up most often during a rebrand or a domain migration, when a large number of published posts need the same edit. If you want to retrieve your posts rather than change them — for an archive or a migration — see [Exporting your Changelog posts](https://help.userflow.com/beamer/docs/en/exporting-your-changelog-posts).

## What isn't available in the dashboard

There's no multi-select on the Changelog dashboard, so you can't bulk archive, bulk expire, or bulk edit posts from the UI. Note that Feedback is different — Ideas do support bulk actions. If you're trying to act on Ideas rather than Changelog posts, see [Performing bulk actions on Ideas](https://help.userflow.com/beamer/docs/en/performing-bulk-actions-on-ideas).

## Using the API

The Beamer API lets you retrieve your posts and update them programmatically, which covers most bulk scenarios:

- Archiving or expiring a batch of old posts — for example, retiring everything published before a rebrand.
- Updating Segment URLs across posts — for example, after moving part of your app to a new domain.
- Changing content or metadata on many posts at once.

The general pattern is to retrieve the posts you want with the `/posts` endpoint, then update each one with the values you need. See our [API documentation](https://help.userflow.com/beamer/docs/en/beamer-api-reference) for the endpoints and authentication.

On limits: there's no per-minute rate limit to design around in normal use. What applies is your account's monthly API call limit, so a large one-off migration is worth checking against your remaining allowance before you start.

## Two things that reduce the work

Before writing a script, check whether either of these solves it without one:

- **Expiration dates.** If you want posts to disappear on a schedule rather than retroactively, set an expiration date on the post instead. See [Scheduling a post (including expiration) in Beamer](https://help.userflow.com/beamer/docs/en/how-can-i-schedule-a-post-including-expiration-on-beamer).
- **Wildcards and multiple URLs in Segment URLs.** A single post can hold several URLs separated by semicolons, and a wildcard such as `https://yourdomain.com/*` can cover a whole section of your site. Structuring your URLs this way up front means a future domain change touches fewer posts.