chatMessageHostedContent resource type
Namespace: microsoft.graph
Important
APIs under the /beta
version in Microsoft Graph are subject to change. Use of these APIs in production applications is not supported. To determine whether an API is available in v1.0, use the Version selector.
Represents Teams content hosted in a chat message, such as images or code snippets. File attachments aren't hosted content; they're stored in SharePoint or OneDrive.
Methods
Method | Return Type | Description |
---|---|---|
List hosted content | chatMessageHostedContent collection | Retrieve the list of chatMessageHostedContent for a message. |
Get hosted content | chatMessageHostedContent | Read the properties and relationships of a chatMessageHostedContent object. |
Properties
chatMessageHostedContent derives from teamworkHostedContent
Property | Type | Description |
---|---|---|
id | String | Read-only. Represents the chat message hosted content identifier. |
contentBytes | Edm.Binary | Write-only. When posting new chat message hosted content, represents the bytes of the payload as a base64 encoded string. |
contentType | String | Write-only. When posting new chat message hosted content, represents the type of content, such as image/png. |
Instance attributes
Instance attributes are properties with special behaviors. These properties are temporary and either define behavior the service should perform or provide short-term property values, like a download URL for an item that expires.
Property name | Type | Description |
---|---|---|
@microsoft.graph.temporaryId | string | Write-only. Represents the temporaryId for the hosted content while posting a message to refer to the hosted content in chatMessage resource being sent. |
Relationships
None.
JSON representation
The following JSON representation shows the resource type.
{
"@microsoft.graph.temporaryId": "String (identifier)",
"id": "String (identifier)",
"contentBytes": "String (binary)",
"contentType": "String"
}
피드백
https://aka.ms/ContentUserFeedback
출시 예정: 2024년 내내 콘텐츠에 대한 피드백 메커니즘으로 GitHub 문제를 단계적으로 폐지하고 이를 새로운 피드백 시스템으로 바꿀 예정입니다. 자세한 내용은 다음을 참조하세요.다음에 대한 사용자 의견 제출 및 보기