Changelog

April 28, 2026

• In the Email Performance API, the Stream events endpoint now provides more detailed event data for email tracking. The eventType field has been extended with a new eventSubType field, offering more granular insights into bounce reaasons. For example, you can identify specific reasons such as a non-existent recipient address, a full mailbox, or a suppressed address, helping you better understand and act on delivery failures.

  Additionally, the eventReadTime field indicates how long recipients spent reading an email, in seconds, enabling deeper analysis of engagement.

April 24, 2026

• The Audit Log API allows you to retrieve audit log entries from your Staffbase platform. Audit log entries capture events related to authentication activity, user account changes, and API token management. For example, failed login attempts, password changes, and API token creations or deletions. Use this API to support security monitoring, incident investigation, and compliance requirements.

• Staffbase API specification files now follow a date-based versioning format (year.month.day), making it easy to identify when an API specification was last updated. This change applies only to newly created or updated API specifications. Whenever an API file is modified, its version will reflect the corresponding update date going forward.

April 23, 2026

• On the API tokens page in the Studio, you can now rotate an API token from the Actions menu. Rotating a token generates a new secret while preserving the token ID and all its permissions. Any systems using the previous secret immediately lose access and must be updated with the new secret. This enhances security by allowing you to rotate API secrets without creating new API tokens.

April 8, 2026

• The CSV Import API now supports two new overwrite options on non delta imports: overwrite all users, or overwrite only users that were previously imported via CSV.

April 2, 2026

• The Groups API now includes a new relevance_DESC sort parameter to retrieve groups based on their relevance to the search query, with the most relevant groups appearing first in the results.

March 1, 2026

• Staffbase APIs no longer return publicly accessible media URLs when fetched with an API token. This means that the media URLs returned by these requests would require authentication. To obtain publicly accessible media URLs, use the Make media URLs public endpoint.

February 26, 2026

• You can now define allowed IP ranges when creating an API token. This lets you restrict token usage to specific source IP addresses or ranges using CIDR notation. If a request is made with the token from an IP address outside the configured ranges, the request is rejected. Use this option to limit token exposure, enforce network-level access control, and reduce the risk of unauthorized use in case a token is compromised.

February 24, 2026

• In the User API, the latest version endpoints are now officially out of beta and is available for production use. The previous version endpoints remain fully supported and continue to work as before. However, Staffbase recommends migrating to the latest version for improved performance and additional features. For more information on the changes and how to migrate, refer to the User API migration guide.

• The User API return metadata endpoint has been removed. This endpoint was deprecated in September 2025.

• The Groups API, which was in beta since October 2025, is now officially out of beta and is available in production. Use it to create and manage groups on the Staffbase platform more efficiently.

February 3, 2026

• In the Pages API the response schema now includes a new field isOutdated. This boolean field indicates whether the page content is outdated based on its update reminder settings. This addition helps you easily identify pages that may require updates or reviews.

February 2, 2026

When retrieving a user via the Users API, the response now includes both the value and source for the userName object, matching the existing structure for email object. Previously, the userName response included only the value. With this change, email and userName behave the same way, making it easier to understand the source as well.

January 30, 2026

• In the User API a new field activatedAt has been added to the user object, indicating the date and time when a user account was activated on the platform.

January 21, 2026

The Groups API now supports filtering group members by their status using the status query parameter.

January 7, 2026

• In the CSV Import API, the import status response now includes a reactivated field in the changes summary alongside existing metrics (created, updated, deactivated, deleted). Previously, reactivated users were not tracked as a separate metric.

December 15, 2025

The Groups API now supports managing group members using externalId in addition to userId. When using the PATCH method to update members, you have more flexibility in how you add or remove users.

November 17, 2025

• In the CSV Import API and the latest User API endpoints, the response Not Found (404) is now returned for single-entity actions when the user does not have permission to perform the action on any of the entities in the request. Previously, a Forbidden (403) response was returned in this case. This change improves security by preventing information leakage about the existence of entities.

November 7, 2025

• The Email Performance API now includes two new endpoints, list emails and get email metadata, to help users retrieve email performance data more efficiently.

November 3, 2025

• The CSV Import API now includes a new endpoint to get the changelog of an import. This allows users to track changes made during CSV imports more effectively.

October 30, 2025

• Introducing the Groups API that simplifies creating and managing groups in your platform. It brings enhanced flexibility and automation, allowing you to integrate groups management into your workflows.

October 28, 2025

• Access to the Tags API is now limited to administrators and group administrators to improve platform security.

October 14, 2025

• When using the latest version of SCIM, the following issues were reported and have now been fixed:
  • In rare cases, profile fields were not updated correctly.
  • User reactivation did not work as expected.

October 8, 2025

• The Chat API now includes a new endpoint to delete group chat conversations. Learn more.

September 24, 2025

• The User API introduces the following updates:
  • New versions of existing endpoints: Several endpoints of the User API now have new versions with improved performance and usability. Staffbase recommends migrating to these versions to benefit from the enhancements. Updated endpoints include:
    • List users
    • Invite users
    • Return a user
    • Delete a user
  • New endpoints: To replace certain legacy behaviors and improve efficiency, the following new endpoints have been added:
    • Update a user
    • Search users
• Deprecated: Return metadata endpoint has been deprecated due to low usage. It is planned to be removed on January 1, 2026. Learn more about Staffbase API lifecycle and deprecation policy.

Use the migration guide to test and plan your migration. Learn more about Staffbase versioning policy before you plan your migration.

September 4, 2025

• The Search Settings API now includes a new parameter redirectUrlMobile in addition to the existing redirectUrl parameter. This allows you to specify a different redirect URL for mobile devices, enhancing the user experience by directing mobile users to a mobile-optimized search engine. If not specified, it defaults to the value of redirectUrl.

August 25, 2025

• The Media API now includes a new endpoint to retrieve publicly accessible media URLs. This makes it easier to share media content for display without requiring authentication. Learn more.

• Starting March 1, 2026, Staffbase APIs will no longer return publicly accessible media URLs when fetched with an API token. This means that the media URLs fetched would require authentication. Instead, publicly accessible media URLs can only be retrieved via the Make media URLs public endpoint. If you use APIs to fetch media files, ensure that you update your implementation accordingly before this date. Learn more.

August 8, 2025

• The CSV Import API is now offically out of beta. It has introduced partialTag property to support partial CSV imports. This is especially useful if you want to:
  • Create conditional groups based on partial CSV tags
  • Migrate to the CSV Import API if you previously used partial CSV imports with the legacy method

• Starting October 31, 2025, the (Legacy) CSV Import API will no longer be offered. If you use it for user management, Staffbase strongly recommends switching to the CSV Import API before this date.

August 7, 2025

• The Update Internal Section endpoint in the Search Settings API now includes the following changes:
  • The request body schema has been updated to accurately reflect the required structure.
  • The iconURL property is now read-only and can no longer be updated.

June 27, 2025

• The Notifications API now offers two new endpoints:

  • Send a notification: Notify specific users or user groups using the notification center, push notifications, or both.

  • Send a plugin notification: Notify specific users or user groups about a particular plugin instance using the notification center, push notifications, or both. This is particularly useful for plugin developers targeting a plugin instance’s audience. Both endpoints allow you to customize the notification’s text, icon, and image for more personalized, context-aware messages.

• In the Notifications API, the two new enhanced endpoints replace the existing Send notifications endpoint, which is now deprecated and scheduled for removal by end of 2025. Staffbase strongly recommends switching to the new endpoints to ensure continued support and access to enhanced functionality.

June 23, 2025

• The Users Sync API is now available for use. Utilize this API to synchronize users from the Staffbase platform, ensuring that your user data is always up-to-date and consistent across your applications.

June 16, 2025

• The Spaces API now includes a new parameter for the Search spaces endpoint. You can now use the relevance_desc parameter to sort search results by relevance in descending order, making it easier to find the most relevant spaces first.

June 13, 2025

• The Media API now includes a new endpoint dedicated for replacing media files. This endpoint allows you to replace existing media files with new ones while maintaining the original URL, ensuring that any references to the original file remain valid. This is particularly useful for updating media content without needing to change links or references in your content.

May 22, 2025

• The File Management API is now offically out of beta. It offers a range of methods to streamline file management tasks on your platform, such as adding files to your File Manager and creating, updating, or deleting collections. Whether you need to import assets from an external source, set up files for a new editor, or manage collections centrally as an administrator, the File Management API makes it simple and efficient. Learn more on getting started with the File Mangement API.

May 5, 2025

• In the Search Settings API, To align with best practices followed across other Staffbase APIs, the following changes have been made:

  • The update internal sections endpoint has been added.
  • The update integration sections endpoint now uses the PUT method instead of PATCH.
  • The update search settings endpoint has been removed as its behavior can be achieved via the other three update endpoints.

May 2, 2025

• The Campaigns API now supports emails assigned to campaigns. It has been updated to reflect recent changes in platform capabilities. The sourceType parameter, which specifies the type of content assigned to a campaign, no longer supports the EXTERNAL_CONTENT value. Instead, a new content source type, EMAIL, has been added to support Staffbase Email.

April 23, 2025

• The Media API now includes a new search endpoint that allows you to search for media items based on the query you provide. This is particularly useful for integrating media results into federated search solutions. The endpoint returns media information that matches the filename, content, or type directly from the Staffbase platform, based on your users’ search input.

April 22, 2025

• The new Search Settings API lets you fine-tune the redesigned search results page to fit your organization’s needs. Show or hide sections and the flyout, rename or reorder sections, set up a custom redirect URL after search input validation, and define which sites or knowledge bases should be searchable in Microsoft or ServiceNow.
• The new Installation API introduces a search endpoint that allows you to search plugins installed on your platform based on the query you provide. This is particularly useful to fetch plugin details into your federated search solutions. The endpoint returns plugin information with accurate relevance and proper permission handling, directly from the Staffbase platform, based on your users’ search input.

April 15, 2025

• The News API now includes a new search endpoint that allows you to search for news posts using a query string. It retrieves a list of news posts that match the search query in the content, hashtags, image descriptions, teasers, or titles of the posts. This is particularly useful for third-party federated search solutions, enabling you to fetch news post details without indexing or storing the data in external systems.

• The new Profile API comes with a search endpoint that allows you to search user profiles using any query text you provide. It searches across all searchable fields within user profiles. This is especially useful for third-party federated search solutions, enabling you to fetch user profile details without indexing or storing the data in external systems.

April 2, 2025

• In the News API, the campaignId parameter has been deprecated in the following endpoints:

  • POST Create a news post
  • PUT Update a news post

  To assign a post to a campaign, use the campaignId parameter in the create campaign reference endpoint of the Campaigns API. The campaignId parameter will be removed from the News API endpoints on November 1, 2025. This change ensures that campaign-related actions are handled consistently through the Campaigns API.

March 27, 2025

• When a user’s avatar image was set to null via an API call, the user was unable to access the Studio. This has been fixed.

February 26, 2025

• Introducing the Email Performance API that retrieves detailed tracking data for emails sent through Staffbase Email. This API provides key performance metrics, including the number of emails sent, opened, and clicked, helping you measure engagement and optimize your communication strategy. Discover more about its capabilities.

• The Spaces API now includes a new endpoint to retrieve a list of spaces using query, filter, and sorting options. Additionally, the newly introduced section array enables you to identify and assign spaces across one or more products available on your platform, such as Employee App, Front Door Intranet, or Staffbase Email.

• In the (New) CSV Import API, the Update CSV import configuration endpoint now includes an additional optional field, type. This parameter defines whether it is a user import or a contact import for Staffbase Email.

February 5, 2025

• The News API now includes a new endpoint dedicated for retrieving acknowledgments on a news post.

February 4, 2025

• In the (New) CSV Import API, the errors response field of an import has been removed. Instead, we are developing a more scalable and user-friendly error reporting functionality with the endpoint /users/imports/{import_Id}/errors.

January 29, 2025

The Quicklinks API now includes a new parameter visibleInPublicArea, which allows Quicklinks to be available in the public area.

This update does not change the default behavior of existing Quicklinks. When creating a new Quicklink, it remains unavailable in the public area by default.

December 10, 2024

• Starting December 10, 2024, Staffbase will discontinue support for the following generic URLs as reply URLs:
  • de.eyo.net (DE)
  • backend.staffbase.com (US)

If you use any of these domains as reply URLs, you must update your Identity Provider (IdP) settings with your Staffbase platform domain to the list of allowed reply URLs. This is essential to avoid disruptions to your API integrations and SAML-SSO authentication flow. If you are impacted, your Customer Success Manager or Support team will reach out to you to assist you further.

October 17, 2024

• Pages API: The Pages API simplifies creating new pages with content from external sources, making it ideal for organizations migrating to the Staffbase platform or consolidating scattered information. It helps preserve valuable content and ensures a seamless transition during migration. Additionally, you can manage your pages using the Pages API.
  Learn more about the Pages API use cases:

  • Extract Page Content Using the Pages API
  • Import External Content to Pages

• File Management API: Introducing File Management API that offers a range of methods to streamline file management tasks on your platform, such as adding files to your File Manager and creating, updating, or deleting collections. Whether you need to import assets from an external source, set up files for a new editor, or manage collections centrally as an administrator, the File Management API makes it simple and efficient. Learn more on getting started with the File Mangement API.

• Spaces API: The Spaces API simplifies creating and managing Spaces in your platform. It brings enhanced flexibility and automation, allowing you to integrate Spaces management into your workflows.

October 1, 2024

• In the Analytics API, the maximum limit for Content and Post ranking has been adjusted to 50000.

September 17, 2024

• In the Notifications API, a new error code has been added to the response of the Send notifications endpoint. The error code 429 is returned when too many requests are sent in parallel and exceeds the rate limits. When this error occurs, wait a short period before retrying the request. To avoid this error, we recommend staggering API calls instead of sending them all at once.

• In the Campaigns API, the Create campaign references endpoint now returns the plannedAt parameter. This parameter shows at what time and date the post is planned to be published and it is returned with the response body. The plannedAt parameter provides a date and time in ISO 8601 format. For example, 2024-09-17T12:00:00Z.

August 31, 2024

• In the User API, the enabled, pending, and verificationCode response fields of a user have been removed, as announced last year. To access the same information, use the following properties instead:
  • status
  • secret

July 30, 2024

• In the Campaigns API, there are now two new endpoints available for adding and removing content pieces as references. They are:
• Create a campaign reference
• Delete a campaign reference

July 17, 2024

• It is now possible to use the vertical bar | as a CSV separator in the (New) CSV Import API.

May 16, 2024

• Introducing the (New) CSV Import API that offers advanced functionalities and an improved user experience. To get started, see the Get Started With New CSV Import guide. Use this beta feature instead of the (Legacy) CSV Import API, which is planned to be deprecated in the future. Staffbase strongly recommends migrating to the new CSV Import API as soon as possible. Learn more.

• Introducing the Quick Links API that allows you to add custom header links to enable quick access to content for your users. Learn more.

April 9, 2024

• In Campaigns API, the sort parameter has been improved. Now, you have the following enum values for the sort parameter:
• updated_DESC - Sort the reference list in descending order based on the last updated date
• created_DESC - Sort the references attached to a campaign based on the date they were created in descending order, from newest to oldest.
• updated_ASC - Sort the references attached to a campaign based on the date they were last updated in ascending order, from oldest to newest.
• scheduledFor_ASC - Sort the reference list in ascending order based on the publishing order.
• scheduledFor_DESC - Sort the reference list in descending order based on the publishing order.
  In addition, the default value has been changed from updated_DESC to created_DESC.

March 6, 2024

• If you use SAML SSO, you now have the option to configure the SAML domain hints. These hints ensure that users don’t attempt to authenticate with the identity provider (IdP) using domains that are not allowed when using the Staffbase platform. To activate this feature, contact Staffbase Support or your Customer Success Manager. It’s worth noting that this feature currently works with Microsoft Entra ID as the IdP, although it may also work with other IdPs.

March 5, 2024

• The content types multipart/form-data and application/x-www-form-urlencoded have been removed from the Chat API.

February 19, 2024

• The user/tags endpoint under the User API has been removed. You can use Tags API instead.

December 31, 2023

• The Leave Webservice and Shift Webservice are no longer available as public Staffbase APIs.

December 1, 2023

• The Profile API is no longer available as a public Staffbase API. You can use User API for the same purposes. Contact Staffbase Support or your Customer Success Manager for more information.

October 25, 2023

• When updating pending user details with the User API, the profile fields were not populated. This has been fixed quickly.

August 31, 2023

• In User API, the verificationCode, pending and enabled response fields of a user account will be removed until 31/08/2024. Instead, you can now use:
• secret for the verificationCode response field
• status for the pending and enabled response fields
• It also replaced the enabled property with the status property to enable or disable a user with a request.

August 10, 2023

• Introducing Tags API for more scalable and user-friendly format for returning tags used in user profiles. The Tags API will replace the user/tags endpoint under the User API. The user/tags endpoint will soon be removed. If you are still using user/tags endpoint, Staffbase recommends migrating to the Tags API.

• Introducing a new addition to the Analytics API: the User timeseries endpoint. This endpoint returns information on total, registered, active, and engaged users for a specific time frame. It comes with significant improvements, offering enhanced functionality and improved performance to ensure your integrations are future-proof.
  As part of this update, the existing User timeseries with SCIM endpoint will be deprecated. Staffbase will continue to support this endpoint until the beginning of 2024, after which it will no longer be supported. Staffbase recommends migrating to the User timeseries endpoint.

July 14, 2023

• Users and tokens assigned as editors on a specific plugin could set properties via API on these plugins, which exceeded their permission level. This has been fixed. Now, users and tokens with editorial access for specific plugins can only set the plugin properties available to them in the Studio user interface.

June 16, 2023

• In User API, the source response field of a user has been removed. Instead, you can now use the creation response field.

May 11, 2023

• Introducing Contact API that allows you to sync your recipients’ email addresses and other attributes from any third-party human resources system directly into Employee Email for creating custom distribution lists.

April 13, 2023

• In User API, the creation date of the user account got incorrectly overwritten with the activation date. This has been fixed.

February 9, 2023

• In News, when the User API was used to search for posts, acknowledgments were not displayed. This has been fixed.