jNewer Version Available
Communications Cloud TM Forum API Release Notes
These features are implemented/enhanced for Spring’26 release.
Extensibility for TMF APIs
Salesforce’s TMF API extensibility framework enables customers to modify standard TMF-compliant APIs to meet specific business requirements while maintaining interoperability and scalability.
Extensibility for TMF629 v4 Customer Management API
For the TMF629 API, extensibility is enabled through Apex lifecycle hooks and customizable GraphQL queries, allowing customers to adjust request and response payloads without compromising TMF compliance. You can perform following operations.
- Extend the main entity with additional fields
- Map a field from a different or related entity
- Customize WHERE clauses at the main entity level
- Customize WHERE clauses at the sub-resource level
- Apply sorting (ORDER BY) on main and sub-resource results
Direct Access to Industry APIs (Inbound)
For the Spring'26, you can directly access and invoke Industry APIs without mandatory routing through a Salesforce managed API gateway.
These options are available for accessing the Industry APIs:
- Direct Access: Invoke APIs directly through Connect/Apex REST endpoints, without routing through the MuleSoft gateway.
- Mule Gateway: Access APIs through MuleSoft-managed endpoints.
These are the key benefits of direct access.
- Invoke APIs from any source, including internal systems
- Enable reuse in automation workflows
- Faster deployment with greater architectural flexibility
- Meet data residency needs by avoiding cross-region routing
NOTE: Starting from the Winter ’27 release, only the Direct Access option will be supported. The MuleSoft gateway option will be deprecated, and customers must update their integrations to use the Connect/Apex REST endpoints for continued access to the inbound APIs.
Let us know so we can improve!