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.
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
| Endpoint |
|---|
| GET /v2/content/{content_id}/comments List the comments on a content post |
| GET /v2/content/{content_id}/comments/{comment_id}/replies List the replies of a given comment on a content post |
Feeds
| Endpoint |
|---|
| GET /v2/feed/posts/{content_id}/comments List the comments on a content post |
| POST /v2/feed/posts/{content_id}/comments Comment on a post in the feed |
| GET /v2/feed/posts/{content_id}/comments/{comment_id}/replies List the replies of a given comment on a content post |
| POST /v2/feed/posts/{content_id}/comments/{comment_id}/{post_number}/replies Reply to a comment on a post in the feed |
| PUT /v2/feed/posts/{content_id}/comments/{comment_id} Update a comment on a post in the feed |
| GET /v2/feed/users/ 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.
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
| 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.