# Changelog

Welcome to the API changelog! This page provides a detailed record of all updates, new features, and upcoming changes to our APIs. Each year is broken down into quarterly releases, with each quarter featuring three sections:

* **New** (for newly added features and endpoints)
* **Updates** (for improvements, modifications, and behavior changes)


This changelog is designed to help you stay informed about the latest developments and prepare for upcoming changes to ensure a smooth experience integrating with our APIs.

# 2026-03-06

## New Endpoints

### Surface user feeds by a user profile

In the Firstup member experience, users can view which posts they've bookmarked, posts they've created themselves, and topics they follow from their user profile. These endpoints allow users to surface this information.

These endpoints are in the [Feeds](https://developers.firstup.io/endpoints/openapi/feeds) section. They require **oauth2_as_a_user** with the required scope `feeds.read`.

userprofilefeedview.png
| Endpoint |
|  --- |
| [GET /v2/feed/profile/bookmarked](https://developers.firstup.io/endpoints/openapi/feeds/listfeedprofilebookmarked) Return a user profile's bookmarked posts |
| [GET /v2/feed/profile/submitted](https://developers.firstup.io/endpoints/openapi/feeds/listfeedprofilesubmitted) Return a user profile's submitted content (user generated content) |
| [GET /v2/feed/profile/channels](https://developers.firstup.io/endpoints/openapi/feeds/listfeedprofilechannels) Return channels followed by a user profile |
| [GET /v2/feed/channels/posts](https://developers.firstup.io/endpoints/openapi/feed-channel-posts/listfeedchannelposts) Return a user's feed of posts for channels |


### Data exports

We have added endpoints that gain access to the Direct Data Export function that exists in Firstup Studio.

These endpoints provide programmatic access to Firstup’s batch export files by exposing a REST wrapper around the existing SFTP/S3 export. They enable you to list available export files for a given data type (users, campaigns, activities), retrieve file metadata (including an opaque file identifier and generation timestamp), and obtain a time-limited presigned download URL to securely fetch the compressed export from Firstup’s managed S3 storage.

The API preserves the existing export cadence and operational semantics (batch exports produced on the established schedule, file retention window and lifecycle), and is designed as a pull-based, batch alternative to DDE2’s SFTP delivery.

These endpoints have been added as a new [Data Export](https://developers.firstup.io/endpoints/openapi/data-exports) section. They allow either **oauth2_as_a_user** or **oauth2_as_a_server** with the required scope `data_exports.read`.

| Endpoint |
|  --- |
| [GET /v2/data_exports/type/{type_name}/latest](https://developers.firstup.io/endpoints/openapi/data-exports/latestexport) Returns metadata and a presigned download URL for the most recent export file of the specified type within the caller's program. |
| [GET /v2/data_exports/type/{type_name}](https://developers.firstup.io/endpoints/openapi/data-exports/listexports) Lists all available export files for a given type. |
| [GET /v2/data_exports/type/{type_name}/files/{file_id}](https://developers.firstup.io/endpoints/openapi/data-exports/showexport) Returns metadata and a presigned download URL for a specific export file identified by its file ID. The file ID is obtained from the list exports endpoint. |


For full details on the Direct Data Export feature, including the metadata returned, see our [knowledge base article](https://support.firstup.io/hc/en-us/articles/38827993603991-Direct-Data-Export-v2).

## Schema Change

### Mandatory Auto-Follow

The `Content.Channel.Post.Resource` now supports the `auto_follow_mandatory` boolean. This allows users to select whether or not a created (or edited) topic (referred to as channels in the API) is automatically mandatory followed by the selected audience/users or not.

This function sets your topic so new and existing/active users automatically follow the topic. When set to true, existing users in the targeted audience(s) immediately opt in to follow the topic. New users begin following the topic upon registering in the community.

This impacts the following endpoints:

| Endpoint |
|  --- |
| [POST /v2/channels](https://developers.firstup.io/endpoints/openapi/content-publishing/createchannel) |
| [GET /v2/channels](https://developers.firstup.io/endpoints/openapi/content-publishing/listchannels) |
| [PUT /v2/channels](https://developers.firstup.io/endpoints/openapi/content-publishing/updatechannel) |


Find our [knolwedge base article](https://support.firstup.io/hc/en-us/articles/4413655133719-Create-or-Edit-a-Topic#01GG5SRZX19X3HHGSJEY47VBG4) on topic settings for further detail.

A slight difference to the setting in Creator Studio. The mandatory auto-follow does not allow users to unfollow the topic.

# 2026-02-03

### Target content to audiences as focused

The **Content** API now allows content to be marked as Focused and to add an audience for focusing.

**Endpoints**

* [POST /v2/content](https://developers.firstup.io/endpoints/openapi/content-publishing/createcontent)
* [PUT /v2/content/{content_id}](https://developers.firstup.io/endpoints/openapi/content-publishing/updatecontent)


Setting the `targeted` boolean value to true sets the piece of content to `true`. This also allows the `groups` array to be used. This attribute lets you select one or multiple audiences to target the piece of content to.

### Delete a comment

This **Feeds** endpoint allows users to delete a comment they previously made.

[DELETE /v2/feed/posts/{content_id}/comments/{comment_id}](https://developers.firstup.io/endpoints/openapi/feeds/deletefeedpostcomment)

### Report a post or comment

We have added two new [Feeds](https://developers.firstup.io/endpoints/openapi/feeds) endpoints:

**Report a post**

[PUT /v2/feed/posts/{content_id}/report](https://developers.firstup.io/endpoints/openapi/feeds/reportfeedpost)

Creates a Report for a specific feed post for a scoped user. The post must be visible to the user or a 404 Not Found response will be returned; for example, this would happen if the content is published to a targeted topic that does not target the user.

This works in the same way as a member experience UI created in Creator Studio:

reportpost.png
**Report a comment**

[PUT /v2/feed/posts/{content_id}/comments/{comment_id}/report](https://developers.firstup.io/endpoints/openapi/feeds/reportfeedpostcomment)

Creates a Report for a specific comment (or reply) to a post for a scoped user. The comment must be visible to the user or a 404 Not Found response will be returned; for example, this would happen if the comment is published to a post in a targeted topic that does not target the user.

reportcomment.png
### @mentions added

This feature introduces @mention functionality within comments and replies in the Partner API, enabling users to directly tag other members in discussions.

@Mentions have been added to the following endpoints:

**Content Publishing**

| Endpoint |
|  --- |
| [GET /v2/content/{content_id}/comments](https://developers.firstup.io/endpoints/openapi/content-publishing/listcontentcomments) List the comments on a content post |
| [GET /v2/content/{content_id}/comments/{comment_id}/replies](https://developers.firstup.io/endpoints/openapi/content-publishing/listcontentcommentreplies) List the replies of a given comment on a content post |


**Feeds**

| Endpoint |
|  --- |
| [GET /v2/feed/posts/{content_id}/comments](https://developers.firstup.io/endpoints/openapi/feeds/listfeedpostcomments) List the comments on a content post |
| [POST /v2/feed/posts/{content_id}/comments](https://developers.firstup.io/endpoints/openapi/feeds/createfeedpostcomment) Comment on a post in the feed |
| [GET /v2/feed/posts/{content_id}/comments/{comment_id}/replies](https://developers.firstup.io/endpoints/openapi/feeds/listfeedpostcommentreplies) List the replies of a given comment on a content post |
| [POST /v2/feed/posts/{content_id}/comments/{comment_id}/{post_number}/replies](https://developers.firstup.io/endpoints/openapi/feeds/createfeedpostcommentreply) Reply to a comment on a post in the feed |
| [PUT /v2/feed/posts/{content_id}/comments/{comment_id}](https://developers.firstup.io/endpoints/openapi/feeds/reportfeedpostcomment) Update a comment on a post in the feed |
| [GET /v2/feed/users/](https://developers.firstup.io/endpoints/openapi/feeds/suggestuser) Query for users that are able to be mentioned (**new** endpoint) |


To correctly mention a user, the `<user_id>` (which is the advocate id) can be used in the following:

`{ref:user:<user_id>}` or `{ref:user::id:<user_id>}`

You can parse out the `user_id` and then look up the user and transform the mention metadata to the actual user’s display_name/name.

For example, `Welcome back @{ref:user:123}! We're happy to have you back on the team.`

### User shortcuts

[GET /v2/shortcuts](https://developers.firstup.io/endpoints/openapi/user-shortcuts/listshortcuts)

This endpoint endpoint provides users with direct access to critical company resources from their homepage, similarly to the 
Shortcuts tray 
 in Firstup's Employee Experience.

usershortcut.png
# 2025

## 2025-Q4

**Updates**

* We have identified a known Okta provisioning error, and documented a workaround. Refer [here](https://developers.firstup.io/usermanagementapi/scim-user-provision) for guidance.
* We have identified an issue with naming SCIM groups (audiences via API). See [here](https://developers.firstup.io/usergroups-audiences/audiencesscimtroubleshootingguide) for guidance.


**Upcoming**

**Expanded reactions**

The Content and Feeds APIs will soon include expanded reactions as part of a "like". Expanded reactions include: 👍, ❤️, 🤗, 🎉, 💡.

Whilst some endpoint descriptions may mention enabling expanded reactions, this functionality may not yet be availale. We'll update you when it is.

## 2025-Q3

**New**

**Soft Launch: Beta API Documentation & Developer Portal**

We’re excited to announce the soft launch of our new API documentation and developer portal!

This beta release introduces a modernized space for exploring and integrating with our APIs. It includes:

* Updated, structured API documentation for easier navigation and understanding.
* Interactive API reference.
* Contextual information, guides and use cases to help you get started quickly.


During this soft launch phase, we’ll be gathering feedback to improve the experience before a full public release.

We’d love your input! If you notice anything missing, confusing, or broken, please share your feedback so we can refine the portal together.

To provide feedback, simply tap the 👎 at bottom of any page.

Screenshot 2025-09-16 at 14.28.10.png
## 2025-Q2

**Updates**

**Assistant Inbox Endpoints Deprecated**

As stated in the Q1 release, these endpoints are now replaced by the new [Notification Center](/notification-center/notification_center_overview) endpoints.

## 2025-Q1

**New**

**New Notification Center Endpoints**

In Q1 2025, we introduced Notification Center endpoints to provide better management and delivery of notifications across the platform. These new API endpoints allow developers to integrate, create, and manage notifications within their applications, offering more control over how messages are delivered and received.

With the Notification Center enhancements, you can now:

* Create, manage, and send notifications directly through the API.
* Retrieve notification details to track delivery statuses and other metadata.
* Filter and group notifications for better user segmentation and personalization.


For further guidance:

* Look [here](https://support.firstup.io/hc/en-us/articles/28923690887191-Notification-Center) for the **Knowledge Base article** to see how this works in our Creator Studio product.
* Look [here](/notification-center/notification_center_overview) for our **API conceptual documentation** on how the endpoints work.
* Look [here](/endpoints/openapi/notification-center) for the **API reference** for the endpoints and their functionality.


**Upcoming**

**Deprection of Assistant Inbox Endpoints**

As part of our ongoing efforts to streamline and improve the user experience, we plan to deprecate the Assistant Inbox endpoints in favor of the new Notification Center functionality. The Notification Center provides more robust features for managing and delivering notifications, which will fully replace the Assistant Inbox.

The Assistant endpoints, which were used to manage inbox-related notifications, will no longer be supported once the transition is complete. Moving forward, all notification management and delivery will be handled via the Notification Center endpoints, which offer enhanced functionality for creating, tracking, and personalizing notifications.

**Endpoints**

| Endpoint | Reason |
|  --- | --- |
| `GET /v2/assistant/inbox_items` | Replaced by `/v2/notification_center/notifications` |
| `GET /v2/assistant/todos` | Replaced by `/v2/notification_center/notifications` |
| `GET /v2/assistant/notifications` | Replaced by `/v2/notification_center/notifications` |
| `PUT /v2/assistant/notifications/{notification_id}/acknowledge` | Removed due to low or no usage |
| `PUT /v2/assistant/notifications/{notification_id}/acknowledge_all` | Removed due to low or no usage |
| `GET /v2/assistant/inbox_items/total_count` | Replaced by `/v2/notification_center/total_count` |


**Why the change?**

* The Notification Center offers greater flexibility, better performance, and more advanced features compared to the Assistant Inbox.
* It provides improved tools for managing notifications, including customization, segmentation, and more detailed reporting.


We encourage developers to migrate to the Notification Center endpoints for a more powerful and future-proof notification experience.