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.

Feed posts: new for_you feed option.

The GET /v2/feed/posts endpoint now supports for_you as a valid value for the name query parameter.

This allows callers to request the user’s personalized “For You” feed through the existing Feed Posts endpoint.

This endpoint is in the Feeds section. It requires oauth2_as_a_user with the required scope feeds.read.

The profile feed endpoints now support an optional user_id query parameter. When provided, the endpoint returns profile information for the specified user. When omitted, the endpoint defaults to the authenticated user.

These endpoints are in the Feeds section. They require oauth2_as_a_user with the required scope feeds.read.

Endpoints changed:

GET /v2/feed/profile/submitted

GET /v2/feed/profile/channels

The Scim.User.SocialChorusExtension schema now supports the pronouns string attribute.

This enables SCIM user records to include a user’s pronouns through the Firstup SocialChorus user extension. The value is nullable.

This impacts SCIM user create, read, update, and patch workflows where the SocialChorus user extension is used.

Example

{
  "urn:SocialChorus:1.0:User": {
    "pronouns": "they/them"
  }
}

Bookmarked profile feed endpoint removed

The GET /v2/feed/profile/bookmarked endpoint has been removed from the OpenAPI specification.

Bookmarked feed content should now be requested through GET /v2/feed/posts?name=bookmarked.

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 section. They require oauth2_as_a_user with the required scope feeds.read.

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 section. They allow either oauth2_as_a_user or oauth2_as_a_server with the required scope data_exports.read.

For full details on the Direct Data Export feature, including the metadata returned, see our knowledge base article.

Further supporting User Documentation can be found here: Supporting User Documentation

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:

Find our knolwedge base article on topic settings for further detail.

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

Endpoints

• POST /v2/content
• PUT /v2/content/{content_id}

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.

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

DELETE /v2/feed/posts/{content_id}/comments/{comment_id}

We have added two new Feeds endpoints:

Report a post

PUT /v2/feed/posts/{content_id}/report

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:

Report a comment

PUT /v2/feed/posts/{content_id}/comments/{comment_id}/report

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.

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

Feeds

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.

GET /v2/shortcuts

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.

Updates

• We have identified a known Okta provisioning error, and documented a workaround. Refer here for guidance.
• We have identified an issue with naming SCIM groups (audiences via API). See here 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.

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.

Updates

Assistant Inbox Endpoints Deprecated

As stated in the Q1 release, these endpoints are now replaced by the new Notification Center endpoints.

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.

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

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.