# TMF632 v5 Party Management API

The Party Management API (TMF632) provides a standardized mechanism for party management, such as creation, update, retrieval, and deletion of parties.

TMF632 supports these resources.

- **Individual** — A person. Individual records are stored as Salesforce Contact records.
- **Organization** — A company or other organization. Organization records are stored as Salesforce Account records.

Using this API you can perform the following operations on individual and organization parties.

- Retrieve the list of parties from the system
- Get party details based on conditions or an ID parameter
- Create a party (individual or organization)
- Update an existing party
- Delete an existing party

:::note
- For TMF Open API release and specification version, see [Industry API Version](/docs/industries/communications/guide/industry_api_version.md).
:::

## Access Methods

Access TMF632 v5 API using Direct Access Connect/Apex REST endpoints.

- See [TMF632 v5 Use Cases](/docs/industries/communications/guide/TMF632use-cases.md) for sample URLs and payloads.
- See [TMF632 v5 Resource Mappings](/docs/industries/communications/guide/tmf632\_resource_mapping.md) for parameter descriptions.

:::important
Starting from the Winter ’27 release, only the Direct Access option is supported for this API.
:::

## Available In

This API is available in the Salesforce platform.

## Prerequisites

- Required: CommsCloudTMFAPI or the CommsCloud platform license.
- Optional: CommunicationsCloudTMFAPIAddOn-1 add-on license.
- Access check: `IndustriesComms.orgHasCommsTMFAPIAccess`.
- To add an Account-to-Account relationship on an Organization resource, create a PartyRoleRelation.
- An individual party contact that has no associated related accounts (a private contact) cannot be linked with an organization party Account.
- If you implement Apex extensibility hooks, annotate the custom Apex class with `@PermGuard('IndustriesComms.orgHasCommsTMFAPIAccess')`.

## Extensibility

This API uses the TMF extensibility framework. For an overview of the framework and the release when extensibility is available for each API, see [Extensibility for TMF APIs](/docs/industries/communications/guide/introduction_ext.md).

For extensibility features, see [Extensibility for TMF632 v5 Party Management](/docs/industries/communications/guide/TMF632\_extensibility.md).

## Sample Apex URL (Direct Access Method)

TMF632 v5 API uses the following URL formats.

| TMF632 Resource | Sample URL                                                                                           |
| --------------- | ---------------------------------------------------------------------------------------------------- |
| Individual      | `{https://MyDomainLoginUrl}/services/data/{{version}}/connect/comms/partymanagement/v5/individual`   |
| Organization    | `{https://MyDomainLoginUrl}/services/data/{{version}}/connect/comms/partymanagement/v5/organization` |

## Use TMF632 v5 API

To access and use the TMF632 v5 API:

1. Authorize and use a connected app and an OAuth 2.0 authorization flow. See [Authorize Access](/docs/industries/communications/guide/authorization.md).
2. Trigger the API call. Refer to the preceding section for sample URLs.
3. Use the TMF632 v5 API resources and endpoints.
   - See [TMF632 v5 Use Cases](/docs/industries/communications/guide/TMF632use-cases.md) for sample URLs and payloads.
   - See [TMF632 v5 Resource Mappings](/docs/industries/communications/guide/tmf632\_resource_mapping.md) for parameter descriptions.
4. Based on the requirements, extend TMF632 v5 API. See [Extensibility for TMF632 v5 Party Management](/docs/industries/communications/guide/TMF632\_extensibility.md).