---
schema_version: "1"
id: 2d8df79a2d6707c63df53eadaa90764263bb05e4c0712aa12796383a523a3ab9
title: Extensibility for TMF APIs
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/industries-integrations/comms/guides/Extensibility/introduction_ext.md
canonical_url: https://developer.salesforce.com/docs/industries/communications/guide/introduction_ext.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: 95e3c4dcc376f5b5037cbfd635054f570d5bbbd08988dd5ab38e0445b9c5efc0
products:
  - Communications Cloud TM Forum API
  - Industries Integrations
---
# 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.
Customers extend TMF schemas through the TMF extension model, and Salesforce provides a backend framework that supports custom mappings, validations, transformations, and lifecycle hooks.

This framework enables customers to implement custom logic and additional attributes across TMF operations while adhering to platform guidelines for scalability, data integrity, and compliance.

## Key Features

- Flexible Field and Entity Mapping

  - Remap TMF payload fields to different Salesforce fields or objects
  - Support both standard and custom entities
  - Extend responses by adding or reshaping fields

- Attribute Extensibility

  - Allow customers to introduce additional TMF fields or sub-resources
  - Map newly added schema elements to Salesforce data structures

- Advanced Query Extensibility

  - Support custom filtering, sorting, and pagination
  - Enable object-level query extensions

- Custom Validations

  - Allow business-specific validation rules to be plugged into the request lifecycle
  - Support pre- and post-processing validation logic

- Transformations and Execution Hooks

  - Provide lifecycle hooks for request/response transformation
  - Support overrides for core transformation, pre-processing, and post-processing logic

- Inbound and Outbound API Extensibility
  - Apply custom logic to incoming API requests and outgoing API responses
  - Enable modifications for TMF (GET/POST/PATCH/DELETE) operations

## Architecture

The following block diagram provides a high-level overview of how the various components are involved in handling extensibility for TMF APIs.
![Extensibility](https://developer.salesforce.com/media/updated_ext_framework.png "Extensibility")

To know more about Apex and GraphQL:

- See [Apex Developer Guide](https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_dev_guide.htm).
- See [GraphQL API](https://developer.salesforce.com/docs/platform/graphql/overview).

## Available In

From Spring'26, extensibility is implemented for TMF629 v4 Customer Management API available in the Salesforce platform.

- [Extensibility for TMF629 v4 Customer Management](https://developer.salesforce.com/docs/industries/communications/Extensibility/TMF629_extensibility.md).

From Summer'26, extensibility is implemented for the following TMF APIs.

- [Extensibility for TMF621 v5 Trouble Ticket Management](https://developer.salesforce.com/docs/industries/communications/Extensibility/TMF621_extensibility.md).
- [Extensibility for TMF637 v4 Product Inventory Management](https://developer.salesforce.com/docs/industries/communications/Extensibility/TMF637_extensibility.md).

From Winter'27, extensibility is implemented for the following TMF APIs.

- [Extensibility for TMF622 v5 Product Ordering Management](https://developer.salesforce.com/docs/industries/communications/Extensibility/TMF622/TMF622_extensibility.md).
- [Extensibility for TMF632 v5 Party Management](https://developer.salesforce.com/docs/industries/communications/Extensibility/TMF632/TMF632_extensibility.md).
- [Extensibility for TMF666 v5 Account Management](https://developer.salesforce.com/docs/industries/communications/Extensibility/TMF666/TMF666_extensibility.md).

## Prerequisites

- The CommsCloud license must be enabled to invoke the TMF629 API.

<!--## Execution Flow

The following block diagram depicts the end-to-end execution flow of a TMF API request, emphasizing the extensibility features of the Communications Cloud platform, where Apex-based hooks allow customization before and after core processing.
![Extensibility Flow](https://developer.salesforce.com/media/extenibility_callflow.png "Extensibility Flow")

- Client sends TMF request
- Communications cloud receives the request
- Java service identifies TMF interface and locates active Apex implementation
- Apex class executes custom logic prior to request processing
  - Performs pre-processing validation checks
  - Applies custom logic to adjust the query parameters
- Returns GraphQL modification instructions
- Java builds GraphQL Query using Apex JSON, executes GraphQL in Salesforce platform
- Apex class executes custom logic after request processing
- Receives core results and default response
- Enriches/transforms response
- Java serializes and sends final API response-->