---
schema_version: "1"
id: 96566b18609134bb768fa0e4fb5fd89fbae3519e901c1be5a60c3e72d47d3479
title: TMF667 v4 Document Management API
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/industries-integrations/comms/guides/TMF667/TMF667.md
canonical_url: https://developer.salesforce.com/docs/industries/communications/guide/TMF667.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: c66962fd04a9eaa2787973f0bacb1205705251d80db15a2a569e8b37780afb13
products:
  - Communications Cloud TM Forum API
  - Industries Integrations
---
# TMF667 v4 Document Management API

The Document Management API (TMF667) offers a standardized approach for handling documents, especially in the context of partnerships. It enables both document creation and retrieval.
This API manages key metadata associated with a document, including details like related parties (for example, author, reviewer, publisher), creation date, version, and lifecycle status. The actual content of the document is referenced by an associated Attachment, with binary content typically accessible through the Attachment.url attribute, which may point to a file or an HTTPS reference.

The Document Management API is certified by TM Forum.

![Certification](https://developer.salesforce.com/media/APIBadge.GOLDwNewLogo.png '{"class": "image-md"}')

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

## Access Methods

For the Spring'26 and Summer'26 releases, TMF667 v4 API can be accessed using either of the following methods.

- **Mule Gateway:** Access API through standard MuleSoft endpoints. For sample URLs, payloads, and parameter descriptions, see [Reference](https://developer.salesforce.com/docs/industries/communications/references/tmf667v4?meta=Summary) section for details on TMF667 v4 API MuleSoft endpoints.
- **Direct Access:** Bypass Mule Gateway using Connect/Apex REST endpoints.
  - See [TMF667 v4 Use Cases](https://developer.salesforce.com/docs/industries/communications/guide/TMF667use-cases.html) section for sample URLs and payloads.
  - See [TMF667 v4 Resource Mappings](https://developer.salesforce.com/docs/industries/communications/guide/tmf667_resource_mapping.html) section for parameter descriptions.

**important:** 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.

## Available In

This API is available in the managed package and Salesforce platform.

## Prerequisites

- The CommsCloud license must be enabled to invoke the TMF667 v4 API.
- Supporting core entity for document is [ContentDocument](https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_contentdocument.htm?q=contentdocument). The mappings are in reference to [ContentVersion](https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_contentversion.htm?q=contentversion).

## Sample Apex URL (Direct Access Method)

TMF667 v4 API uses the this URL format:
`{https://MyDomainLoginUrl}/services/data/{{version}}/connect/comms/document/v4/document`.

## Use TMF667 v4 API

To access and use the TMF667 v4 API:

1. Authorize and use a connected app and an OAuth 2.0 authorization flow. See [Authorize Access](https://developer.salesforce.com/docs/industries/communications/authorization.md).
2. Trigger the API call. Refer the above section for sample URL.
3. Use the TMF667 v4 API resources and endpoints.
   - See [TMF667 v4 Use Cases](https://developer.salesforce.com/docs/industries/communications/guide/TMF667use-cases.html) section for sample URLs and payloads.
   - See [TMF667 v4 Resource Mappings](https://developer.salesforce.com/docs/industries/communications/guide/tmf667_resource_mapping.html) section for parameter descriptions.