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.