For the TMF666 API, extensibility is enabled through Apex lifecycle hooks and customizable GraphQL queries and mutations. These extension points let customers validate and transform requests, customize Billing Account persistence, and enrich API processing without changing the TMF666 contract.
You can use the extension points to:
- Extend Billing Accounts with additional fields.
- Map fields from Billing Account and related Salesforce records.
- Customize GET fields, filters, sorting, and nested GraphQL selections.
- Apply custom request validations.
- Customize POST, PATCH, and DELETE mutations.
- Refine GET processing and run post-operation logic.
- Enforce customer-specific rules before a Billing Account is deactivated.
TMF666 v5 currently supports the billingAccount resource.
important: - For access methods, prerequisites, and using the API, see TMF666 v5 Account Management API.
Supported Interfaces and Hooks
| Interface Name | Hooks Used by the Operation | Primary Customization |
|---|---|---|
IAccountManagementGET |
transformRequest<br>configureDefaultValidations<br>applyCustomValidations<br>customiseGraphQLQuery<br>handlePostOperation |
Customize Billing Account queries and post-processing |
IAccountManagementPOST |
transformRequest<br>configureDefaultValidations<br>applyCustomValidations<br>customiseMutationPayload<br>handlePostOperation |
Validate and customize Billing Account creation |
IAccountManagementPATCH |
transformRequest<br>configureDefaultValidations<br>applyCustomValidations<br>customiseMutationPayload<br>handlePostOperation |
Validate and customize partial Billing Account updates |
IAccountManagementDELETE |
transformRequest<br>configureDefaultValidations<br>applyCustomValidations<br>customiseMutationPayload<br>handlePostOperation |
Validate and customize logical Billing Account deletion |
IAccountManagementGET inherits from ICommsGET and the common ICommsExtensible contract.