- Managed Entities are detected out-of-the-box in four categories: PII (personally identifiable information), PCI (payments card industry), PHI (personal health information), and General.
- Custom Entities can now be created, updated, and deleted using the Management API, based on the specific vocabulary for your use case.
- For more information, see the Entity Detection docs.
- Entities are now enabled by default for Async APIs.
- Get Entities response fields are updated. To learn more, visit the Get Entities page.
- Optimized API Explorer Trackers flow for the new Managed Trackers capabilities.
- Updated the user interface of the Usage page to align with the aesthetic of the new Platform visual design.
- Fixed issue in API Explorer when a user selects to re-use a conversation but none exist.
- Fixed issue with how App ID and App Secret were displayed in API Explorer.
- Fixed issue in Playground where the selected language was not displayed correctly in the Streaming Conversation code view.
- The Managed Trackers Library consists of out-of-the-box Trackers in four categories: Sales, Contact Center, Recruitment, and General.
- Managed Trackers are curated and managed by Symbl.ai. Sign in to the Symbl.ai Platform to use Trackers from the Managed Trackers Library as per your use case.
- Trackers Recommendations are suggestions from Symbl.ai for which trackers you should use from the Managed Trackers Library based on the conversations you have processed in the last 30 days.
- For more information, see the docs at Trackers .
- Trackers are now enabled by default for Async API and Streaming API.
- Trackers Management API endpoint is now standardized to https://api.symbl.ai/v1/manage/trackers.
- All trackers must now be created via the Management API.
- New PATCH endpoint for Update Tracker operation.
- Tracker resource has two new fields:
- Introducing Async API Logs on the Symbl.ai Platform. Sign in to platform.symbl.ai and go to API Logs > Async API Logs.
- Async API Log entries summarize an API call, listing call method, conversation ID, endpoint, and timestamp. From the Async API Logs page you can drill down to see details including job ID, query parameters, and request / response. For more information, see the docs at Async API Logs.
- Added support for reusing previous conversations in API Explorer.
- Added Symbl SDKs to the Code View inside the Streaming experience in Playground; added direct links to SDKs.
- Updated API Explorer Authentication response to correctly display the
expiresInvalue when using the same token.
- Corrected the URI for API Explorer.
- Changed the initial state of the response body to be empty in API Explorer until the user has made a request.
- Corrected the Header name for API Explorer request samples to be Authorization instead of Authentication.
- Various UX fixes.
Updated docs include:
Introducing the API Explorer, a REST API interface that gives you the ability to test and explore APIs with a just few clicks. Simply log in to platform.symbl.ai, then complete round-trip API requests and responses directly in the platform.
The new platform experience enables you to process conversation data, test APIs, and explore all of our features without writing a single line of code.
Web SDK new release: Version 1.0.5 of the Symbl Web SDK is now available.
- Validation of keys in
StreamingAPIConnectionConfigwhen passed into
- Removed or updated vulnerable NPM dependencies.
- Validation of keys in
Web SDK new release: Version 1.0.4 of the Symbl Web SDK is now available.
- Added extra validation to
- Check if WebSocket is connected when making a
modifySampleRatecall. If not, throw a
- Added reconnection support. If
reconnectOnErroris set to
truein the SymblConfig, Web SDK attempts to reconnect after a break in connection. A break in connection is determined after thirty (30) seconds of not receiving any expected data from the WebSocket.
- Added separate methods to handle
<audio>elements in audiostreams. Web SDK now has
updateVideoSourceElement. Previous versions allowed either
<audio>elements to be passed into the same
attachAudioSourceElement, but going forward only the new separate corresponding methods may be used depending on element type.
SubscribeAPIConnection. These will only be populated after the
conversation_createdevent has been fired. For more information on the
conversation_createdevent, see Events and Callbacks.
- Added a
Conversationobject which can also be used to get the conversation ID. This object is attached to
connection.conversation. Going forward, the
Conversationobject will integrate with Conversation APIs.
- Added extra validation to
- Summary API new release: An updated Summary API is now available.
- Enabling All Trackers with Streaming API: Streaming API now supports enabling all the Trackers associated with an account. Read more here.
- Trackers Limit Increase: Increased Tracker creation limit to 500 per account.
- Summarization Alpha Release: Summary API is now available in the Alpha release phase.
- Relative timestamp for Messages API (LABS):
Added support for the parameters
durationthe Messages API. Read more here.
- Nomenclature Change: Change of name for the parameter
customVocabularyfor Topics API to
customTopicVocabulary. Backward compatibility available.